From: James Bottomley <James.Bottomley@HansenPartnership•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle•com>
Subject: Re: linux-next: Signed-off-by missing for commits in the scsi tree
Date: Tue, 08 Aug 2017 16:41:36 -0700 [thread overview]
Message-ID: <1502235696.2736.120.camel@HansenPartnership.com> (raw)
In-Reply-To: <20170809092730.1138bf7e@canb.auug.org.au>
On Wed, 2017-08-09 at 09:27 +1000, Stephen Rothwell wrote:
> Hi James,
>
> The commit series
>
> 94b76dcac422 ("scsi: qla2xxx: Fix system crash while triggering FW
> dump")
> to
> b96b8da34c40 ("scsi: aacraid: Fix out of bounds in
> aac_get_name_resp")
>
> is missing Signed-off-bys from its committer. It looks like you have
> rebased a series from Martin ...
Yes we had to drop a commit which proved problematic in the fixes tree.
The rule, I believe, is that only the person who transforms the email
to a git tree should be the last signoff in the commit log, even if
they're a tree pulling into another one and thereafter the signoffs go
in the merge commit, so the signoff sent by me in the signed tag when I
send the main tree to Linus is my signoff for transmitting all the
commits, which includes the rebased ones in this instance.
James
next prev parent reply other threads:[~2017-08-08 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 23:27 linux-next: Signed-off-by missing for commits in the scsi tree Stephen Rothwell
2017-08-08 23:41 ` James Bottomley [this message]
2017-08-08 23:53 ` Stephen Rothwell
2017-08-09 16:24 ` Martin K. Petersen
2017-08-09 16:32 ` James Bottomley
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=1502235696.2736.120.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=martin.petersen@oracle$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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