mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
To: Hoeze <git.ich@frhoelzlwimmer.de>,
	lee.jones@linaro.org, linux-kernel@vger.kernel.org
Cc: coolstarorganization@gmail.com, mykesx@gmail.com,
	bjodah@gmail.com, dja@axtens.net,
	Hoeze <Hoeze@github.map.fastly.net>
Subject: Re: [PATCH v3] Fix missing PCI ID; Necessary for Lenovo Yoga 720-15 Touchpad.
Date: Wed, 16 Aug 2017 15:58:38 +1000	[thread overview]
Message-ID: <86d9a2bf-e6b9-bbf1-52ad-c11a00179ebf@au1.ibm.com> (raw)
In-Reply-To: <20170812201620.20129-1-git.ich@frhoelzlwimmer.de>

Hi Florian,

As Daniel said, good work on figuring out how to get this far!

There's a couple of minor issues with the formatting of this patch.

Firstly, as Lee said in response to the last version, you should change 
the summary line of the commit to indicate the contents of the patch 
more accurately.

Based on what I see in the git log, I'd suggest:

	"mfd: intel-lpss: Add missing PCI ID"

The previous commits to this file also mention the type of chipset - I 
*think* this is Sunrise Point, but I don't work for Intel. :)

Don't mention the Lenovo touchpad in the summary - in the main body of 
the commit message is better.

On 13/08/17 06:16, Hoeze wrote:
> From: Hoeze <Hoeze@users.noreply.github.com>

The name and email here is what's going to appear in the git commit log 
as the author of the commit. Generally, it should be the same as both 
the details in your Signed-off-by line, and the email should be the same 
as the email address you're sending from. If the name/email address in 
the commit is the same as the name/email address you're sending from, 
git send-email will actually skip this line completely.

You should probably try:

	$ git config --global user.name "Florian R. Hölzlwimmer"
	$ git config --global user.email "git.ich@frhoelzlwimmer.de"
	$ git commit --amend --reset-author

This will set your details in your git configuration, and then re-create 
the last commit using the correct authorship details.

If you then re-send it, it should skip this From: line and everything 
should be fine.


Andrew

-- 
Andrew Donnellan              OzLabs, ADL Canberra
andrew.donnellan@au1.ibm.com  IBM Australia Limited

      parent reply	other threads:[~2017-08-16  5:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-12 20:16 Hoeze
2017-08-16  0:48 ` Daniel Axtens
2017-08-16  5:58 ` Andrew Donnellan [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=86d9a2bf-e6b9-bbf1-52ad-c11a00179ebf@au1.ibm.com \
    --to=andrew.donnellan@au1.ibm.com \
    --cc=Hoeze@github.map.fastly.net \
    --cc=bjodah@gmail.com \
    --cc=coolstarorganization@gmail.com \
    --cc=dja@axtens.net \
    --cc=git.ich@frhoelzlwimmer.de \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mykesx@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

all inboxes | Powered by JetHome®