linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jitendra Bhivare <jitendra.bhivare@broadcom.com>,
	Ketan Mukadam <ketan.mukadam@broadcom.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the scsi-mkp tree
Date: Thu, 21 Jun 2018 07:30:58 +1000	[thread overview]
Message-ID: <20180621073058.32b95241@canb.auug.org.au> (raw)
In-Reply-To: <yq1h8lxe7mm.fsf@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 410 bytes --]

Hi Martin,

On Wed, 20 Jun 2018 12:37:53 -0400 "Martin K. Petersen" <martin.petersen@oracle.com> wrote:
>
> >> Fixed, thanks!  
> >
> > Unfortunately, James had already merged your tree :-(  
> 
> James' script will drop the offending original commit when I amend
> something in the SCSI tree. So the discrepancy will go away next time he
> updates.

OK, thanks.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-06-20 21:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19 11:15 linux-next: Signed-off-by missing for commit in the scsi-mkp tree Stephen Rothwell
2018-06-20  2:03 ` Martin K. Petersen
2018-06-20  4:54   ` Stephen Rothwell
2018-06-20 16:37     ` Martin K. Petersen
2018-06-20 21:30       ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-12  3:26 Stephen Rothwell
2019-11-19  9:30 Stephen Rothwell
2019-11-20  2:39 ` Martin K. Petersen
2018-03-22  2:14 Stephen Rothwell
2017-08-08  3:26 Stephen Rothwell
2017-08-08  4:49 ` Finn Thain

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=20180621073058.32b95241@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jitendra.bhivare@broadcom.com \
    --cc=ketan.mukadam@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).