From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH v3] of: replace Asahi Kasei Corp venter prefix
Date: Fri, 14 Nov 2014 10:35:56 +0100 [thread overview]
Message-ID: <20141114093554.GC3810@ulmo> (raw)
In-Reply-To: <87k32yd0bd.wl%kuninori.morimoto.gx@renesas.com>
On Fri, Nov 14, 2014 at 01:43:03AM +0000, Kuninori Morimoto wrote:
> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>
> Current vendor-prefixes.txt already has
> "ak" prefix for Asahi Kasei Corp by
> ae8c4209af2cec065fef15d200a42a04130799f7
It's usually enough to show the first 12 (or so) characters of the SHA1
here. git will show you the right one if you do something like:
git log --abbrev=12 --abbrev-commit
It's probably useful to "git config core.abbrev 12" for Linux kernel
repositories.
Other than that it seems like you're being overly careful about not
exceeding 72 characters. Your lines seem to wrap at around less than
50 columns. However, making lines too short results in equally hard to
read commit messages, so please try to shoot for 72 columns for maximum
readability.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141114/b6f807cf/attachment.sig>
next prev parent reply other threads:[~2014-11-14 9:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5398AB07.4040304@wwwdotorg.org>
[not found] ` <87sinbdk44.wl%kuninori.morimoto.gx@renesas.com>
[not found] ` <878ulzx6hr.wl%kuninori.morimoto.gx@gmail.com>
[not found] ` <20140922130026.GK3290@leverpostej>
[not found] ` <CAMuHMdX22z97SbGS1HDiYfJ1PXxyEN2S8D7w4sr+4bUwD+mJZw@mail.gmail.com>
[not found] ` <20140922132743.GM3290@leverpostej>
[not found] ` <87y4rfhmgl.wl%kuninori.morimoto.gx@renesas.com>
[not found] ` <1415845309.4269.6.camel@perches.com>
[not found] ` <20141113025105.GA16652@verge.net.au>
[not found] ` <87vbmjhj00.wl%kuninori.morimoto.gx@renesas.com>
[not found] ` <20141113110740.GE3815@sirena.org.uk>
2014-11-14 1:43 ` [PATCH v3] of: replace Asahi Kasei Corp venter prefix Kuninori Morimoto
2014-11-14 8:38 ` Alexandre Courbot
2014-11-14 9:16 ` Arnd Bergmann
2014-11-14 9:30 ` Thierry Reding
2014-11-14 9:35 ` Thierry Reding [this message]
2014-11-17 0:51 ` [PATCH v4] " Kuninori Morimoto
2014-11-17 10:26 ` Sergei Shtylyov
2014-11-18 0:30 ` [PATCH v5] of: replace Asahi Kasei Corp vendor prefix Kuninori Morimoto
2014-11-28 0:22 ` [PATCH v5][resend] of: replace Asahi Kasei Corp venter prefix Kuninori Morimoto
2014-11-28 11:45 ` Sergei Shtylyov
2014-12-02 4:57 ` [PATCH v5][resend] of: replace Asahi Kasei Corp vendor prefix Kuninori Morimoto
2014-12-15 3:53 ` [PATCH v5][resend v2] " Kuninori Morimoto
2014-12-17 2:33 ` [PATCH v5][resend v3] " Kuninori Morimoto
2015-01-09 3:40 ` [PATCH v5][resend v4] " Kuninori Morimoto
2015-01-09 3:42 ` [PATCH v5][resend v5] " Kuninori Morimoto
2015-01-09 4:36 ` [PATCH v5][resend v4] " Stephen Warren
2015-01-09 10:07 ` Kuninori Morimoto
2015-01-09 13:46 ` Rob Herring
2015-01-09 13:55 ` Arnd Bergmann
2015-01-09 16:04 ` Mark Brown
2014-12-25 3:55 ` [PATCH v5][resend v6] " Kuninori Morimoto
2015-01-13 20:03 ` [PATCH v5][resend] " Rob Herring
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=20141114093554.GC3810@ulmo \
--to=thierry.reding@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).