From: Tony Zelenoff <antonz@parallels.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Love, Robert W" <robert.w.love@intel.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] fcoe: fix compilation warnings of section mismatch
Date: Sat, 30 Jun 2012 09:25:16 +0400 [thread overview]
Message-ID: <4FEE8DBC.9060809@parallels.com> (raw)
In-Reply-To: <1341001228.2907.61.camel@dabdike.int.hansenpartnership.com>
30/06/12 12:20 AM, James Bottomley пишет:
> On Fri, 2012-06-29 at 20:13 +0000, Love, Robert W wrote:
>> On 12-06-26 05:17 AM, Tony Zelenoff wrote:
>>
>> Fix this message:
>> WARNING: drivers/scsi/fcoe/libfcoe.o(.init.text+0x21): Section mismatch
>> in reference from the function init_module() to the function
>> .exit.text:fcoe_transport_exit()
>> The function __init init_module() references
>> a function __exit fcoe_transport_exit().
>>
>> Signed-off-by: Tony Zelenoff <antonz@parallels.com><mailto:antonz@parallels.com>
>>
>>
>> Thank you for the patch. However, this was fixed a few weeks ago. The patch is in James' 'for-next' branch here: http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=43b8a1613a1c8707d0e86316a7d6999fd767a5cf
MAke this patch from linux branch is faster than cloning scsi-next. :)
Anyway, if it fixed - it is nice.
>> I'm not sure if it's queue'd up for the current RC phase or not. I don't know how the scsi.git branches are managed. I think the patch should go for the current RC.
>
> Show me the bug it actually produces and I'll queue it for -rc ...
It mostly cosmetic issue, there is no reason to port it to RC branches.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-06-30 5:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 12:17 [PATCH] fcoe: fix compilation warnings of section mismatch Tony Zelenoff
2012-06-29 20:13 ` Love, Robert W
2012-06-29 20:20 ` James Bottomley
2012-06-30 5:25 ` Tony Zelenoff [this message]
2012-07-02 16:22 ` Rustad, Mark D
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=4FEE8DBC.9060809@parallels.com \
--to=antonz@parallels.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=robert.w.love@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.