The warning appears in W=2 builds. I had another way to silence it by using
diagnostic control macros, but those macros were not accepted. Using a single
designated initialization also silences it.
Sent from my iPhone
> On Oct 17, 2014, at 8:26 AM, "Christoph Hellwig" wrote:
>
>> On Tue, Oct
On Jul 18, 2012, at 10:17 AM, Michael S. Tsirkin wrote:
>> You do have to pay very close attention to some things however. Don't change
>> the device identity in any way - even version information, otherwise a
>> Windows initiator will blue-screen. I made that mistake myself, so I
>> remember
On Jul 18, 2012, at 9:00 AM, Michael S. Tsirkin wrote:
> On Wed, Jul 18, 2012 at 11:53:38AM -0400, Christoph Hellwig wrote:
>> On Wed, Jul 18, 2012 at 08:42:21AM -0500, Anthony Liguori wrote:
>>>
>>> If you add support for a new command, you need to provide userspace
>>> a way to disable this com
On Jul 11, 2012, at 4:02 AM, Heiko Carstens wrote:
> Fix this warning:
>
> WARNING: drivers/scsi/fcoe/libfcoe.o(.init.text+0x7c):
> Section mismatch in reference from the function init_module()
> to the function .exit.text:fcoe_transport_exit()
As far as I can see, resolving this issue only requ
4 matches
Mail list logo
