From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Michael Chan <mchan@broadcom.com>
Cc: Anil Veerabhadrappa <anilgv@broadcom.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"michaelc@cs.wisc.edu" <michaelc@cs.wisc.edu>
Subject: Re: [PATCH 1/3] bnx2i remove not so useful global variable bnx2i_reg_devices
Date: Sun, 28 Jun 2009 15:11:10 -0500 [thread overview]
Message-ID: <1246219871.4190.25.camel@mulgrave.site> (raw)
In-Reply-To: <1246219164.839.31.camel@nseg_linux_HP1.broadcom.com>
On Sun, 2009-06-28 at 12:59 -0700, Michael Chan wrote:
> On Sun, 2009-06-28 at 10:25 -0700, James Bottomley wrote:
> > On Sun, 2009-06-28 at 08:46 -0700, Michael Chan wrote:
> > > James Bottomley wrote:
> > >
> > > > On Tue, 2009-06-23 at 18:11 -0700, Anil Veerabhadrappa wrote:
> > > > > >From a8267738e9ca5c73ad6c0d89f17cf864bfc908c8 Mon Sep 17
> > > > 00:00:00 2001
> > > > > From: Anil Veerabhadrappa <anilgv@broadcom.com>
> > > > > Date: Tue, 23 Jun 2009 13:56:29 -0700
> > > > > Subject: [PATCH] bnx2i - remove global variable
> > > > bnx2i_reg_devices
> > > > >
> > > > > * Removed bnx2i_reg_devices as this counter is not really
> > > > > used in a meaningful way
> > > > > Cc: Mike Christie <michaelc@cs.wisc.edu>
> > > > >
> > > > > Signed-off-by: Michael Chan <mchan@broadcom.com>
> > > > > Signed-off-by: Anil Veerabhadrappa <anilgv@broadcom.com>
> > > >
> > > > Tell me what these signoffs mean: The first signoff by Michael Chan
> > > > implies it's his patch, but it has your authorship information.
> > > >
> > >
> > > Sorry, Anil should have put his signoff first. Do we need to re-spin
> > > the pacthes?
> >
> > So did you actually contribute to these? In which case a note saying
> > something like
> >
> > [mchan: did X to the driver]
>
> Here's one example of what I did:
>
> [mchan: bnx2i_init_one() - don't add hba to adater_list if
> ->register_device fails ]
>
> In general, all our patchsets go through some internal review and
> testing by others besides the author. We use multiple signoffs to
> include everyone who has made some contributions to the patchset. We'll
> try to be more specific about who did what in the future.
That's fine ... and including what they actually did with square
brackets is a good way of reminding me that the usage is correct.
Many people use signed-off-by to award recognition, but that's not what
they're for: they're there because of SCO and the need to track patches
back to sources according to the Developer Certificate of Origin. Under
the DCO a signed-off-by means the person in the signoff modified the
patch in some way (or retransmitted it).
James
next prev parent reply other threads:[~2009-06-28 20:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 1:11 [PATCH 1/3] bnx2i remove not so useful global variable bnx2i_reg_devices Anil Veerabhadrappa
2009-06-24 20:00 ` Mike Christie
2009-06-28 14:33 ` James Bottomley
2009-06-28 15:46 ` Michael Chan
2009-06-28 17:25 ` James Bottomley
2009-06-28 19:59 ` Michael Chan
2009-06-28 20:11 ` James Bottomley [this message]
2009-07-09 1:21 ` [PATCH] BNX2I: register given device with cnic if shost != NULL in ep_connect() Anil Veerabhadrappa
2009-07-09 6:21 ` Mike Christie
2009-07-09 7:15 ` Michael Chan
2009-07-09 14:39 ` Anil Veerabhadrappa
2009-07-09 17:43 ` Mike Christie
2009-07-09 20:32 ` Anil Veerabhadrappa
2009-07-09 20:49 ` Anil Veerabhadrappa
2009-07-30 4:49 ` [PATCH 1/2] bnx2i : Fix CMDSN jump issue seen during cable pull test Anil Veerabhadrappa
2009-07-30 15:31 ` Mike Christie
2009-09-11 17:38 ` [PATCH 1/1] BNX2I - Fix context mapping issue for architectures with PAGE_SIZE != 4096 Anil Veerabhadrappa
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=1246219871.4190.25.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=anilgv@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=michaelc@cs.wisc.edu \
/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