From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Martin Sperl <kernel-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org>
Cc: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
lee-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rpi-kernel
<linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH 1/6] spi: bcm2835: remove dependency on handle_err which is
Date: Mon, 30 Mar 2015 21:13:00 -0600 [thread overview]
Message-ID: <551A10BC.1010607@wwwdotorg.org> (raw)
In-Reply-To: <20150329164818.GO1743-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On 03/29/2015 10:48 AM, Mark Brown wrote:
> On Sun, Mar 29, 2015 at 04:03:22PM +0200, Martin Sperl wrote:
>> in spi-for-next
>>
>> Remove the implementation of handle_err, the function of which
>> was introduced to spi-for-next with patch b716c4ff
>
> Why?
>
> When referencing patches please include the patch title as well as
> the hash, this makes the mail/commit log more directly readable by
> humans.
I believe these days it's also typical to use a 12-character commit
hash when referencing commits; IIRC Linus suggested the following in
your ~/.gitconfig:
[core]
abbrev = 12
... which would yield the following:
$ git log --oneline -1 b716c4ff|cat
b716c4ffc6a2 spi: introduce master->handle_err() callback
... so you'd typically write the following in a commit log:
b716c4ffc6a2 (spi: introduce master->handle_err() callback)
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-03-31 3:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 14:03 [PATCH 1/6] spi: bcm2835: remove dependency on handle_err which is Martin Sperl
[not found] ` <72441EEF-C509-433B-9DBA-53A936ED5BDB-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org>
2015-03-29 16:48 ` Mark Brown
[not found] ` <20150329164818.GO1743-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-03-29 17:03 ` Martin Sperl
[not found] ` <119C0671-7379-483A-B734-441E6354633E-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org>
2015-03-29 18:21 ` Mark Brown
2015-03-31 3:13 ` Stephen Warren [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=551A10BC.1010607@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=kernel-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org \
--cc=lee-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).