public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Joe Perches <joe@perches.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	Trivial patch monkey <trivial@kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	kernel list <linux-kernel@vger.kernel.org>,
	tony@atomide.com, daniel.baluta@intel.com, andrew@lunn.ch,
	baolin.wang@linaro.org, rteysseyre@gmail.com,
	javier.martin@vista-silicon.com, sandeep_n@ti.com,
	dmurphy@ti.com, juhosg@openwrt.org, andy.yan@rock-chips.com,
	robdclark@gmail.com, srinivas.kandagatla@linaro.org,
	steven.eckhoff.opensource@gmail.com
Subject: Re: [PATCH][trivial] fix email address quoting in MODULE_AUTHOR()
Date: Mon, 24 Dec 2018 06:30:58 +0000	[thread overview]
Message-ID: <20181224063058.GA4846@dell> (raw)
In-Reply-To: <b80c5fcd621e19255f824acb521984dbf845b9ed.camel@perches.com>

On Sun, 23 Dec 2018, Joe Perches wrote:

> On Sun, 2018-12-23 at 20:27 +0100, Pavel Machek wrote:
> >     
> > Apparently it is quite easy to forget ">" in quoting of email
> > address. This fixes it.
> 
> It's good you do this, thanks.
> 
> Please use git diff --stat -p when you produce these
> or git format-patch so there is an easy to read list
> of files modified in this patch.

`git format-patch` & `git send-email` is preferred.

I would also suggest that you split this up into patch-per-subsystem
set for easy merge, since there aren't *any* dependencies between
them.

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2018-12-24  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-23 19:27 [PATCH][trivial] fix email address quoting in MODULE_AUTHOR() Pavel Machek
2018-12-23 19:58 ` Joe Perches
2018-12-24  6:30   ` Lee Jones [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=20181224063058.GA4846@dell \
    --to=lee.jones@linaro.org \
    --cc=akpm@osdl.org \
    --cc=andrew@lunn.ch \
    --cc=andy.yan@rock-chips.com \
    --cc=baolin.wang@linaro.org \
    --cc=daniel.baluta@intel.com \
    --cc=dmurphy@ti.com \
    --cc=javier.martin@vista-silicon.com \
    --cc=joe@perches.com \
    --cc=juhosg@openwrt.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=robdclark@gmail.com \
    --cc=rteysseyre@gmail.com \
    --cc=sandeep_n@ti.com \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=steven.eckhoff.opensource@gmail.com \
    --cc=tony@atomide.com \
    --cc=trivial@kernel.org \
    /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