linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Phu Luu <Phu.Luu@silabs.com>
Cc: "johan@kernel.org" <johan@kernel.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Brant Merryman" <Brant.Merryman@silabs.com>,
	"Richard Hendricks" <Richard.Hendricks@silabs.com>,
	"hungnd3@fsoft.com.vn" <hungnd3@fsoft.com.vn>,
	"Phú Lưu An" <luuanphu@gmail.com>
Subject: Re: [PATCH v3 1/2] USB: serial: cp210x: Enable usb generic throttle/unthrottle
Date: Fri, 26 Jun 2020 09:36:57 +0200	[thread overview]
Message-ID: <20200626073657.GO3334@localhost> (raw)
In-Reply-To: <57401AF3-9961-461F-95E1-F8AFC2105F5E@silabs.com>

On Fri, Jun 26, 2020 at 04:22:58AM +0000, Phu Luu wrote:
> From: Brant Merryman <brant.merryman@silabs.com>
> 
> Assign the .throttle and .unthrottle functions to be generic function
> in the driver structure to prevent data loss that can otherwise occur
> if the host does not enable USB throttling.
> 
> Signed-off-by: Phu Luu <phu.luu@silabs.com>
> Signed-off-by: Brant Merryman <brant.merryman@silabs.com>

Almost there. As I mentioned, the authori's SOB goes first and the
following SOB lines indicates who forwarded the patch (e.g. you in this
case).

If you also contributed to the patch you (e.g. you added the missing
changelog text) you should also add a Co-developed-by tag as described
in the process document I referred to:

	Co-developed-by: states that the patch was co-created by
	multiple developers; it is a used to give attribution to
	co-authors (in addition to the author attributed by the From:
	tag) when several people work on a single patch.  Since
	Co-developed-by: denotes authorship, every Co-developed-by: must
	be immediately followed by a Signed-off-by: of the associated
	co-author.  Standard sign-off procedure applies, i.e. the
	ordering of Signed-off-by: tags should reflect the chronological
	history of the patch insofar as possible, regardless of whether
	the author is attributed via From: or Co-developed-by:.
	Notably, the last Signed-off-by: must always be that of the
	developer submitting the patch.

	- Documentation/process/submitting-patches.rst

So in this case the tags should probably be:

	SOB: Brant
	CDB: Phu
	SOB: Phu

Care to fix that up in a v4 (yes, please increment the patch revision
every time you resubmit)?

Johan

  reply	other threads:[~2020-06-26  7:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26  4:22 [PATCH v3 1/2] USB: serial: cp210x: Enable usb generic throttle/unthrottle Phu Luu
2020-06-26  7:36 ` Johan Hovold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-06-24  7:01 Phu Luu
2020-06-24  7:43 ` Johan Hovold

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=20200626073657.GO3334@localhost \
    --to=johan@kernel.org \
    --cc=Brant.Merryman@silabs.com \
    --cc=Phu.Luu@silabs.com \
    --cc=Richard.Hendricks@silabs.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hungnd3@fsoft.com.vn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=luuanphu@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).