linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.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>,
	Mike Marciniszyn <mike.marciniszyn@intel.com>,
	Kaike Wan <kaike.wan@intel.com>,
	Dennis Dalessandro <dennis.dalessandro@intel.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the rdma tree
Date: Fri, 1 Sep 2017 08:06:59 -0400	[thread overview]
Message-ID: <78c70af4-21d0-94f2-6a2d-a832f24d23f4@redhat.com> (raw)
In-Reply-To: <20170901075046.557e345c@canb.auug.org.au>


[-- Attachment #1.1: Type: text/plain, Size: 455 bytes --]

On 8/31/2017 5:50 PM, Stephen Rothwell wrote:
> Hi Doug,
> 
> Commit
> 
>   4b9796b0a6fb ("IB/hfi1: Use accessor to determine ring size")
> 
> is missing a Signed-off-by from its author.
> 

What's the best way to fix this?  I can rebase, but I know Linus hates
that.  What about git note?

-- 
Doug Ledford <dledford@redhat.com>
    GPG Key ID: B826A3330E572FDD
    Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD


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

  reply	other threads:[~2017-09-01 12:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 21:50 linux-next: Signed-off-by missing for commit in the rdma tree Stephen Rothwell
2017-09-01 12:06 ` Doug Ledford [this message]
2017-09-02 16:42   ` Linus Torvalds
2018-11-08 22:13 Stephen Rothwell
2021-04-08 22:00 Stephen Rothwell
2021-04-09 16:20 ` Dennis Dalessandro
2021-04-09 16:46   ` Jason Gunthorpe
2022-10-27 19:33 Stephen Rothwell
2022-10-28 16:16 ` Jason Gunthorpe

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=78c70af4-21d0-94f2-6a2d-a832f24d23f4@redhat.com \
    --to=dledford@redhat.com \
    --cc=dennis.dalessandro@intel.com \
    --cc=kaike.wan@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mike.marciniszyn@intel.com \
    --cc=sfr@canb.auug.org.au \
    /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).