mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ashutosh Naik <ashutosh.naik@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: ketuzsezr@darnok.org, James.Bottomley@hansenpartnership.com,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	pjones@redhat.com, konradr@linux.vnet.ibm.com,
	vishnu@chelsio.com
Subject: Re: [PATCH]ibft: Fix the display of a few fields in the NIC attribute  structure in sysfs
Date: Mon, 20 Apr 2009 21:30:00 +0530	[thread overview]
Message-ID: <81083a450904200900p7f885bf6v1d50a3429293e2f1@mail.gmail.com> (raw)
In-Reply-To: <20090415143744.84d6c598.akpm@linux-foundation.org>

On Thu, Apr 16, 2009 at 3:07 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> 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.
<snip>

> 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.

Sorry for the delay.

Here is an updated Changelog

The patch ensures that on, if the DHCP

      parent reply	other threads:[~2009-04-20 16:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-11 13:29 Ashutosh Naik
2009-04-11 17:34 ` Konrad Rzeszutek
2009-04-11 17:56 ` James Bottomley
2009-04-11 18:13   ` Ashutosh Naik
2009-04-12 13:06   ` Konrad Rzeszutek
2009-04-15 21:37     ` Andrew Morton
2009-04-20 15:59       ` Ashutosh Naik
2009-04-20 16:00       ` Ashutosh Naik [this message]

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=81083a450904200900p7f885bf6v1d50a3429293e2f1@mail.gmail.com \
    --to=ashutosh.naik@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=ketuzsezr@darnok.org \
    --cc=konradr@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pjones@redhat.com \
    --cc=vishnu@chelsio.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 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®