From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: "Eric Dumazet" <dada1@cosmosbay.com>
Cc: "kernel list" <linux-kernel@vger.kernel.org>,
"Vladislav Bolkhovitin" <vst@vlnb.net>,
"Alexander Shishkin" <alexander.shishckin@gmail.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Geert Uytterhoeven" <geert@linux-m68k.org>
Subject: Re: A question about sparse: how to use __acquires() and __releases() correctly ?
Date: Thu, 4 Dec 2008 15:04:19 +0100 [thread overview]
Message-ID: <e2e108260812040604s1eab8744g8f2fd63d27373af4@mail.gmail.com> (raw)
In-Reply-To: <4937DB1E.7060500@cosmosbay.com>
On Thu, Dec 4, 2008 at 2:29 PM, Eric Dumazet <dada1@cosmosbay.com> wrote:
> The sparse version I have here doesn't complain on dev_seq_stop() in
> net/core/dev.c
I have been running sparse on a tree built with a .config file
generated by 'make allmodconfig'. Could this be an explanation ?
Bart.
next prev parent reply other threads:[~2008-12-04 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 19:59 Bart Van Assche
2008-12-04 12:12 ` Bart Van Assche
2008-12-04 13:06 ` Johannes Berg
2008-12-04 13:29 ` Eric Dumazet
2008-12-04 14:04 ` Bart Van Assche [this message]
2008-12-04 14:12 ` Eric Dumazet
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=e2e108260812040604s1eab8744g8f2fd63d27373af4@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=alexander.shishckin@gmail.com \
--cc=dada1@cosmosbay.com \
--cc=geert@linux-m68k.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vst@vlnb.net \
/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
all inboxes | Powered by JetHome®