From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Rich Felker <dalias-8zAoT0mYgF4@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] spi: Split bus and I/O locking
Date: Thu, 28 Jul 2016 10:59:32 +0100 [thread overview]
Message-ID: <20160728095932.GC11806@sirena.org.uk> (raw)
In-Reply-To: <20160728022314.GG15995-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
On Wed, Jul 27, 2016 at 10:23:14PM -0400, Rich Felker wrote:
> I saw it's in the asoc tree now -- will this be making it upstream for
> this merge window? Hoping so. The issue it fixes is a nasty data
> corruption regression that's been around for a while now and although
> we can keep using out-of-tree patches or workarounds it would be nice
> to have it fixed in unpatched kernels. Thanks again for the quick
> patch and for doing it in a way that makes the code clearer & more
> accessible to developers reading and trying to understand it.
It was sent to Linus via the SPI tree earlier this week, the message
about ASoC was a result of a misfiring script.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-07-28 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 23:12 [PATCH] spi: Split bus and I/O locking Mark Brown
[not found] ` <1469142737-2814-1-git-send-email-broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-07-22 0:17 ` Rich Felker
2016-07-28 2:23 ` Rich Felker
[not found] ` <20160728022314.GG15995-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org>
2016-07-28 9:59 ` Mark Brown [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=20160728095932.GC11806@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=dalias-8zAoT0mYgF4@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).