linux-pwm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Nick Vaccaro <nvaccaro@google.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
	linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] FIXUP: CHROMIUM: fix transposed param settings
Date: Fri, 23 Jun 2017 14:17:58 -0700	[thread overview]
Message-ID: <20170623211757.GA145579@google.com> (raw)
In-Reply-To: <CAME0mb0RJ81FBixF-u3Pq7+iJoLKLkqZJiFSdm25_rHCfw_Msw@mail.gmail.com>

(Kernel mailing lists don't usually like HTML mail. Gmail web interface
can get plain text if you really try, in one of the 'compose' options.
But it'll always screw up patch formatting, so it's only worth light
use)

On Fri, Jun 23, 2017 at 02:04:44PM -0700, Nick Vaccaro wrote:
>    Hi Brian,
>    Thanks for the info, I'm new to this process.

No problem, and understood.

>    I was asked to create a FIXUP CL and send it upstream.  Not knowing
>    format of a "FIXUP" cl, I looked at other FIXUP cl's in the chromeos
>    kernel and followed suit.

There are various reasons we might use a "FIXUP" prefix within the
Chrome OS kernel; among them: a patch might diverge upstream, as it gets
reviewed, but we might already have applied the patch to our tree.

In this case, you have a totally new patch.

[If you wanted to represent the "FIXUP" concept here, you might use a
tag like this, before the Signed-off-by:

Fixes: 1f0d3bb02785 ("pwm: Add ChromeOS EC PWM driver")
]

If in doubt, check the git log for examples (as you did already), but
note that there are different practices for mainline Linux and for the
Chromium OS, as Chromium OS is a downstream project.

>    I emailed it upstream with a "FIXUP: CHROMIUM:" prefix. Should I change
>    the checkin comment title line to "[PATCH] pwm: cros-ec: fix transposed
>    param settings" and resend the email?

Yes, that'd be all.

(And you can include my 'Reviewed-by:' tag when you resend.)

>    Please advise, thanks.

Brian

      reply	other threads:[~2017-06-23 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 17:54 [PATCH] FIXUP: CHROMIUM: fix transposed param settings Nick Vaccaro
2017-06-23 20:23 ` Brian Norris
2017-06-23 21:04   ` Nick Vaccaro
2017-06-23 21:17     ` Brian Norris [this message]

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=20170623211757.GA145579@google.com \
    --to=briannorris@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=nvaccaro@google.com \
    --cc=thierry.reding@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).