linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Paul Walmsley <paul.walmsley@sifive.com>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Andreas Schwab <schwab@suse.de>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	linux-kernel@lists.kernel.org
Subject: Re: [PATCH] Use CSR numbers instead of names
Date: Wed, 7 Aug 2019 08:49:25 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.9999.1908070848550.13971@viisi.sifive.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1908070842400.13971@viisi.sifive.com>

On Wed, 7 Aug 2019, Paul Walmsley wrote:

> On Wed, 7 Aug 2019, Bin Meng wrote:
> 
> > On Wed, Aug 7, 2019 at 1:40 PM Christoph Hellwig <hch@infradead.org> wrote:
> > >
> > > On Tue, Aug 06, 2019 at 06:39:59PM -0700, Paul Walmsley wrote:
> > > > >
> > > > > I have already sent a similar patch (with more places fixed) on Jul 11.
> > > > > https://patchwork.kernel.org/patch/11039421/
> > > >
> > > > Christoph's patch predates yours.
> > > >
> > > > If all looks well with your patch, I'll update it to remove the overlap
> > > > and queue it after his.
> > >
> > > The one from Bin looks most comprehensive, so maybe go with that, plus
> > > the hunk from Andreas for the instance that was only recently introduced.
> > 
> > Thanks Christoph.
> > 
> > I've included your SoB and Andreas's into my v2 patch which added the
> > changes of arch/riscv/mm/init.c that was recently changed.
> > https://patchwork.kernel.org/patch/11082147/
> 
> Best not to add others' Signed-off-by:s unless they explicitly offer them. 
> Adding a Signed-off-by: for the kernel denotes that that person has 
> accepted the Developer's Statement of Origin here:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n431
> 
> Could you please either convert those into Co-developed-by: lines or ask 

Actually even Co-developed-by: lines require Signed-off-by:s as well:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n548

- Paul

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2019-08-07 15:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 13:40 [PATCH] Use CSR numbers instead of names Andreas Schwab
2019-08-05 15:05 ` Anup Patel
2019-08-06 20:49 ` Christoph Hellwig
2019-08-07  0:04   ` Paul Walmsley
2019-08-07  1:31     ` Bin Meng
2019-08-07  1:39       ` Paul Walmsley
2019-08-07  5:40         ` Christoph Hellwig
2019-08-07 13:34           ` Bin Meng
2019-08-07 15:13             ` Christoph Hellwig
2019-08-07 15:47             ` Paul Walmsley
2019-08-07 15:49               ` Paul Walmsley [this message]
2019-08-07 16:09               ` Bin Meng

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=alpine.DEB.2.21.9999.1908070848550.13971@viisi.sifive.com \
    --to=paul.walmsley@sifive.com \
    --cc=bmeng.cn@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@lists.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=schwab@suse.de \
    /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).