linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Darren Hart <dvhart@infradead.org>
Cc: Alberto Ponces <ponces26@gmail.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	Hans de Goede <hdegoede@redhat.com>,
	Andy Shevchenko <andy@infradead.org>,
	Platform Driver <platform-driver-x86@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] platform/x86: silead_dmi: Add touchscreen platform data for the Teclast X3 Plus tablet
Date: Tue, 23 Jan 2018 17:18:44 -0800	[thread overview]
Message-ID: <20180124011844.k4hfwujev2jkjetk@dtor-ws> (raw)
In-Reply-To: <20180124010259.GJ16464@fury>

On Tue, Jan 23, 2018 at 05:02:59PM -0800, Darren Hart wrote:
> On Tue, Jan 23, 2018 at 04:37:43PM -0800, Dmitry Torokhov wrote:
> > On Tue, Jan 23, 2018 at 3:27 PM, Darren Hart <dvhart@infradead.org> wrote:
> > > On Tue, Jan 23, 2018 at 06:33:38PM +0000, Alberto Ponces wrote:
> > >> Add touchscreen platform data for the Teclast X3 Plus tablet.
> > >>
> > >> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
> > >>
> > >> Signed-off-by: Alberto Ponces <ponces26@gmail.com>
> > >
> > > Queued, thanks.
> > >
> > > Note for the future: Author signoff goes first, then reviewers, then committer.
> > 
> > In this case Alberto was the committer, so his sign-off is last, as it
> > should be. Any reported-by, suggested-by, acked-by or reviewed-by he
> > collected should go above his sign-off. Once you picked up his patch
> > you 'll become committer, so any markings you add should go between
> > his sign-off and yours.
> 
> Of course, you're correct. Thank you for the correction - and Alberto, apologies
> for the noise/confusion.
> 
> Dmitry, I reviewed documentation/process/submitting-patches.rst and
> 5.Posting.rst and didn't find this clearly defined. Have I missed where this is
> documented, or is an update in order?

I do not think is was ever stated explicitly, the closest comes "14) The
canonical patch format" which states that sign off goes before the ---
divider.

I think it comes naturally if you consider patch vs pull request: if you
decided to pull from Alberto's tree (or anyone else's tree) instead of
taking the patch via email, then if they'd put non-sign-off tags after
the sign-off, they'd end up in your and then Linus' tree like that, as
you would not add your sign-off when doing git merge.

But if you believe this should be called explicitly then adding a few
more words to section 14 should work.

Thanks.

-- 
Dmitry

  reply	other threads:[~2018-01-24  1:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 11:18 [PATCH] Add touchscreen platform data for the Teclast X3 Plus tablet Alberto Ponces
2018-01-23 14:50 ` Hans de Goede
2018-01-23 18:33 ` [PATCH v2] platform/x86: silead_dmi: " Alberto Ponces
2018-01-23 23:27   ` Darren Hart
2018-01-24  0:37     ` Dmitry Torokhov
2018-01-24  1:02       ` Darren Hart
2018-01-24  1:18         ` Dmitry Torokhov [this message]
2018-01-24  9:51           ` Alberto Ponces

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=20180124011844.k4hfwujev2jkjetk@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=andy@infradead.org \
    --cc=dvhart@infradead.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=ponces26@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;
as well as URLs for NNTP newsgroup(s).