linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Ettle <james@ettle.org.uk>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the nfsd tree
Date: Fri, 23 Feb 2018 12:41:05 +0000	[thread overview]
Message-ID: <440587E4-661C-4E73-A954-8329593DAE4F@ettle.org.uk> (raw)
In-Reply-To: <20180223010545.GC15876@fieldses.org>

Hello,

I'm OK with that. (This is the first time I've ventured into kernel space so I thought it better to at least sketch a solution and let the experts do it correctly ;) Glad it's passed the review!)

Thanks,
James.

On 23 February 2018 01:05:45 GMT+00:00, "J. Bruce Fields" <bfields@fieldses.org> wrote:
>On Thu, Feb 22, 2018 at 06:39:43AM +0000, James Ettle wrote:
>> I only really posted this as a demo of a fix. I was hoping someone
>who actually knows what they're doing in the kernel would pick it up
>and make it proper.
>
>Whoops, sorry, I didn't realize that.
>
>But I don't see a problem with the patch as it is.  Are you OK with me
>adding your signed-off-by?
>
>--b.
>
>> 
>> Thanks,
>> James.
>> 
>> 
>> On 22 February 2018 04:17:23 GMT+00:00, Stephen Rothwell
><sfr@canb.auug.org.au> wrote:
>> >Hi,
>> >
>> >Commit
>> >
>> >  35da1ba8af70 ("sunrpc: Fix unaligned access on sparc64")
>> >
>> >is missing a Signed-off-by from its author.
>> >
>> >-- 
>> >Cheers,
>> >Stephen Rothwell

  reply	other threads:[~2018-02-23 12:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22  4:17 linux-next: Signed-off-by missing for commit in the nfsd tree Stephen Rothwell
     [not found] ` <12138EE4-77CA-480F-B2F9-B4C7E4E20891@ettle.org.uk>
2018-02-23  1:05   ` J. Bruce Fields
2018-02-23 12:41     ` James Ettle [this message]
2018-02-23 15:20       ` J. Bruce Fields
  -- strict thread matches above, loose matches on Subject: below --
2021-11-22 21:15 Stephen Rothwell
2021-05-20 22:04 Stephen Rothwell
2021-05-21 13:50 ` J. Bruce Fields
2021-05-21 13:55   ` Kornievskaia, Olga
2021-05-21 14:01     ` J. Bruce Fields
2021-05-21 14:42       ` Kornievskaia, Olga
2021-05-21 14:53         ` J. Bruce Fields
2020-11-08 21:20 Stephen Rothwell
2020-11-08 21:29 ` J. Bruce Fields
2020-11-09  9:15   ` Dan Carpenter
2019-12-21  3:10 Stephen Rothwell
2019-12-02 20:38 Stephen Rothwell
2017-11-27 22:52 Stephen Rothwell
2017-11-28  1:38 ` J. Bruce Fields
2017-11-28  2:02   ` Stephen Rothwell
2017-11-09 19:51 Stephen Rothwell
2017-11-09 20:06 ` J. Bruce Fields
2017-08-24 22:48 Stephen Rothwell
2017-08-25  2:21 ` J. Bruce Fields
2017-08-25  2:37   ` J. Bruce Fields

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=440587E4-661C-4E73-A954-8329593DAE4F@ettle.org.uk \
    --to=james@ettle.org.uk \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).