From: Ramkumar Ramachandra <artagnon@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] Trivial sparse acquire/release annotations
Date: Sat, 6 Jul 2013 17:41:23 +0530 [thread overview]
Message-ID: <1373112686-28501-1-git-send-email-artagnon@gmail.com> (raw)
Hi,
So, I was looking at sparse this lazy Saturday afternoon. Thought I
might as well clean up a few obvious warnings while I'm there.
Thanks.
Ramkumar Ramachandra (3):
nfs: add lock annotations to squelch sparse warnings
apic: add lock annotations to squelch sparse warnings
irq: add lock annotation to squelch a sparse warning
arch/x86/kernel/apic/io_apic.c | 2 ++
fs/nfs/client.c | 4 ++++
kernel/irq/irqdesc.c | 1 +
3 files changed, 7 insertions(+)
--
1.8.3.2.733.gf8abaeb
next reply other threads:[~2013-07-06 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-06 12:11 Ramkumar Ramachandra [this message]
2013-07-06 12:11 ` [PATCH 1/3] nfs: add lock annotations to squelch sparse warnings Ramkumar Ramachandra
2013-07-06 12:11 ` [PATCH 2/3] apic: " Ramkumar Ramachandra
2013-07-06 12:11 ` [PATCH 3/3] irq: add lock annotation to squelch a sparse warning Ramkumar Ramachandra
2013-09-23 14:41 ` [PATCH 0/3] Trivial sparse acquire/release annotations Ramkumar Ramachandra
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=1373112686-28501-1-git-send-email-artagnon@gmail.com \
--to=artagnon@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®