From: Josh Triplett <josh@freedesktop.org>
To: Christopher Li <sparse@chrisli.org>
Cc: Alexey Dobriyan <adobriyan@sw.ru>,
linux-sparse@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: sparse breakage triggered by rcu_read_lock() lockdep annotations
Date: Sat, 20 Oct 2007 20:34:04 -0700 [thread overview]
Message-ID: <471AC8AC.7020701@freedesktop.org> (raw)
In-Reply-To: <70318cbf0710191408mfb372bah292028f7bafb6eec@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 318 bytes --]
Christopher Li wrote:
> OK, I get a trivial fix after all. The test case is fixed now.
> I haven't done much test otherwise.
>
> See the patch attached.
Nice work Chris! Patch applied and pushed out.
I may roll an 0.4.1 release in the near future to fix kernel
builds with Sparse.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2007-10-21 3:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 10:55 sparse breakage triggered by rcu_read_lock() lockdep annotations Alexey Dobriyan
2007-10-18 17:41 ` Josh Triplett
2007-10-19 19:44 ` Chris Li
2007-10-19 21:08 ` [PATCH] " Christopher Li
2007-10-21 3:34 ` Josh Triplett [this message]
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=471AC8AC.7020701@freedesktop.org \
--to=josh@freedesktop.org \
--cc=adobriyan@sw.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
/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 NNTP newsgroup(s).