From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-sparse@vger.kernel.org
Subject: Re: lock context warnings
Date: Wed, 7 Jan 2009 12:20:18 +0300 [thread overview]
Message-ID: <f19298770901070120v396222d9g1d0ea7b78cbc07c9@mail.gmail.com> (raw)
In-Reply-To: <20090107084539.GA15246@lst.de>
On Wed, Jan 7, 2009 at 11:45, Christoph Hellwig <hch@lst.de> wrote:
> Since a few month sparse keeps spewing tons of wrong lock context
> warnings like:
Yes, the warnings are wrong, and the patches that were supposeed to
fix them breoke other things, so they were never merged.
Christopher reverted the patches that introduced the new warnings
in his tree: git://git.kernel.org/pub/scm/devel/sparse/chrisl/sparse.git
until someone fixes or rewrites the context checking.
It looks like Christopher is serious about maintaining this tree, so
people should probably switch to using it.
next prev parent reply other threads:[~2009-01-07 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 8:45 lock context warnings Christoph Hellwig
2009-01-07 9:20 ` Alexey Zaytsev [this message]
2009-01-07 16:34 ` Christoph Hellwig
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=f19298770901070120v396222d9g1d0ea7b78cbc07c9@mail.gmail.com \
--to=alexey.zaytsev@gmail.com \
--cc=hch@lst.de \
--cc=linux-sparse@vger.kernel.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).