From: Rakib Mullick <rakib.mullick@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: axboe@kernel.dk, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] block: Mark virtio_blk with __refdata in virtio_blk.c
Date: Fri, 17 Jul 2009 20:13:22 +0600 [thread overview]
Message-ID: <b9df5fa10907170713u508f5c3br2463d0fc0ba0515@mail.gmail.com> (raw)
In-Reply-To: <4A6013F3.1030101@kernel.org>
On 7/17/09, Tejun Heo <tj@kernel.org> wrote:
> Hello,
>
> Generally looks good to me.
>
>
> > +/* We were warned by false positive warning, so __refdata comes into rescue. */
> > +static struct virtio_driver __refdata virtio_blk = {
>
>
> But it would be nicer if the comment contains a bit more of detail.
> Can you please beef it up a bit? After that I'll queue it in my temp
> tree and send to Linus' way.
>
Ok. Assuming that changelog is ok. I'm just sending the patch here
with a beefed up comment. Hopefully everyone will like it. If not or
if requires resend please notice.
Thanks,
----
Signed-off-by: Rakib Mullick <rakib.mullick@gmail.com>
--- linus/drivers/block/virtio_blk.c 2009-07-17 21:07:40.000000000 +0600
+++ rakib/drivers/block/virtio_blk.c 2009-07-17 21:14:36.000000000 +0600
@@ -424,7 +424,13 @@ static unsigned int features[] = {
VIRTIO_BLK_F_SCSI, VIRTIO_BLK_F_IDENTIFY
};
-static struct virtio_driver virtio_blk = {
+/*
+ * virtio_blk messes up by simultaneously refering to a __devinit and
+ * a __devexit function. Which causes a false positive warning. So we
+ * use __refdata to avoid this warning.
+ */
+
+static struct virtio_driver __refdata virtio_blk = {
.feature_table = features,
.feature_table_size = ARRAY_SIZE(features),
.driver.name = KBUILD_MODNAME,
next prev parent reply other threads:[~2009-07-17 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-12 11:13 Rakib Mullick
2009-07-17 6:02 ` Tejun Heo
2009-07-17 14:13 ` Rakib Mullick [this message]
2009-07-19 1:48 ` Tejun Heo
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=b9df5fa10907170713u508f5c3br2463d0fc0ba0515@mail.gmail.com \
--to=rakib.mullick@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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®