public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Trond Myklebust <trondmy@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: List Linux Next Mailing <linux-next@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: linux-next: Signed-off-by missing for commit in the nfs tree
Date: Thu, 31 May 2018 15:24:10 +1000	[thread overview]
Message-ID: <87y3g0tn2d.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAABAsM7VZcJvtSnbebOAWEAZ7oTkV6JXJF=GxOj=zLYgjSGQ_Q@mail.gmail.com>

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

On Wed, May 30 2018, Trond Myklebust wrote:

> Hi Stephen,
>
> Thanks for noticing and apologies for missing that. I'll take that
> patch out until Neil can update it.
>

Thanks for noticing that Stephen,
I've sent and updated version.

Thanks,
NeilBrown


> Cheers
>   Trond
> On Wed, 30 May 2018 at 17:26, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> Hi Trond,
>>
>> Commit
>>
>>   f217ebf24480 ("NFS: slight optimization for walking list for delegations")
>>
>> is missing a Signed-off-by from its author.
>>
>> --
>> Cheers,
>> Stephen Rothwell

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2018-05-31  5:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 21:26 linux-next: Signed-off-by missing for commit in the nfs tree Stephen Rothwell
2018-05-30 22:22 ` Trond Myklebust
2018-05-30 22:26   ` Trond Myklebust
2018-05-31  0:42     ` Stephen Rothwell
2018-05-31  5:24   ` NeilBrown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-14 21:58 Stephen Rothwell
2025-07-14 22:29 ` Trond Myklebust

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=87y3g0tn2d.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=trondmy@gmail.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