From: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>, linux-sparse@vger.kernel.org
Subject: Re: [sparse] forgotten patch
Date: Tue, 25 Jul 2023 08:20:53 +0200 (CEST) [thread overview]
Message-ID: <732ac78e-9161-1fe5-f2eb-ec6f773814cb@intel.com> (raw)
In-Reply-To: <f6cf3f45-87de-f29b-8ace-f837772b21c@intel.com>
Hi,
Could you please pull the below patch. We've been using a private branch
for SOF CI for 8 months now and this isn't a good place to be at:
https://github.com/thesofproject/sof/blob/a38458dd2276fa24e37f5e60ef0a5613b03cbe00/.github/workflows/sparse-zephyr.yml#L33
Thanks
Guennadi
On Tue, 18 Apr 2023, Guennadi Liakhovetski wrote:
> Hi,
>
> Looks like this patch https://marc.info/?l=linux-sparse&m=166861736724543&w=2
> has been forgotten? In general - where is the sparse development taking place
> ATM - the https://git.kernel.org/pub/scm/devel/sparse/sparse.git/ repo seems
> to not have been updated since last June?
>
> Thanks
> Guennadi
>
parent reply other threads:[~2023-07-25 6:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <f6cf3f45-87de-f29b-8ace-f837772b21c@intel.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=732ac78e-9161-1fe5-f2eb-ec6f773814cb@intel.com \
--to=guennadi.liakhovetski@linux.intel.com \
--cc=acme@kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).