lkml.org 
[lkml]   [2009]   [Apr]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH]ibft: Fix the display of a few fields in the NIC attribute structure in sysfs
On Sun, 12 Apr 2009 09:06:59 -0400
Konrad Rzeszutek <ketuzsezr@darnok.org> wrote:

> > The second question is who picks this up? The drivers/firmware
> > directory doesn't seem to have a dedicated tree, so I can take this
> > through the SCSI tree if required or Andrew can take it through -mm.
>
> Which way works best for everybody? I was thinking SCSI, since the end result
> of this module is to configure the storage used to bootstrap the box.

I can merge merge it later this week.

However...


: From: Ashutosh Naik <ashutosh.naik@gmail.com>
:
: Fix the display of a few fields in the iBFT NIC attribute structure in
: sysfs.
:
: Signed-off-by: Ashutosh Naik <ashutosh.naik@gmail.com>
: Cc: Vishnu V <vishnu@chelsio.com>
: Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
: ---
:
: drivers/firmware/iscsi_ibft.c | 4 ++--
: 1 file changed, 2 insertions(+), 2 deletions(-)
:
: diff -puN drivers/firmware/iscsi_ibft.c~ibft-fix-the-display-of-a-few-fields-in-the-nic-attribute-structure-in-sysfs drivers/firmware/iscsi_ibft.c
: --- a/drivers/firmware/iscsi_ibft.c~ibft-fix-the-display-of-a-few-fields-in-the-nic-attribute-structure-in-sysfs
: +++ a/drivers/firmware/iscsi_ibft.c
: @@ -754,11 +754,11 @@ static int __init ibft_check_nic_for(str
: rc = 1;
: break;
: case ibft_eth_ip_addr:
: - if (!memcmp(nic->dhcp, nulls, sizeof(nic->dhcp)))
: + if (memcmp(nic->ip_addr, nulls, sizeof(nic->ip_addr)))
: rc = 1;
: break;
: case ibft_eth_subnet_mask:
: - if (!memcmp(nic->dhcp, nulls, sizeof(nic->dhcp)))
: + if (nic->subnet_mask_prefix)
: rc = 1;
: break;
: case ibft_eth_origin:

The changelog is bad.

What does "fix" mean? What does the old output look like and how does
this patch change it?

This matters, because this is a userspace interface and who knows, there
might be applications out there which somehow depend on the old and
broken behaviour.

Of course, that might be totally silly and unrealistic but because we
weren't told what the patch actually does, how can I tell?

Please send a new and complete description of this change, thanks.



\
 
 \ /
  Last update: 2009-04-15 23:47    [W:0.091 / U:0.108 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site