mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ashutosh Naik <ashutosh.naik@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	Andrew Morton <akpm@osdl.org>,
	pjones@redhat.com, konradr@linux.vnet.ibm.com,
	ketuzsezr@darnok.org, "Vishnu V. Mandyam" <vishnu@chelsio.com>
Subject: Re: [PATCH]ibft: Fix the display of a few fields in the NIC attribute  structure in sysfs
Date: Sat, 11 Apr 2009 10:56:07 -0700	[thread overview]
Message-ID: <1239472568.3416.11.camel@mulgrave.int.hansenpartnership.com> (raw)
In-Reply-To: <81083a450904110629j93c5c2j2c1250e9822c3888@mail.gmail.com>

On Sat, 2009-04-11 at 18:59 +0530, Ashutosh Naik wrote:
> This patch fixes the display of a few fields in the iBFT NIC attribute
> structure in sysfs.
> 
> Signed-off-by: Ashutosh Naik <ashutosh.naik@gmail.com>
> Signed-off-by: Vishnu V<vishnu@chelsio.com>

What do these signoffs mean?  Traditionally you sign off on a patch if
it passed through your hands, so if this is a patch from Vishnu which
you're sending in, they need to be in reverse order (and a From: for
Vishnu).

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.

James



  parent reply	other threads:[~2009-04-11 17:56 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 [this message]
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

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=1239472568.3416.11.camel@mulgrave.int.hansenpartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=akpm@osdl.org \
    --cc=ashutosh.naik@gmail.com \
    --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®