From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] spi: mxs: Assign message status after transfer finished
Date: Fri, 26 Oct 2012 15:13:47 +0200 [thread overview]
Message-ID: <201210261513.47664.marex@denx.de> (raw)
In-Reply-To: <20121026130459.GW18814@opensource.wolfsonmicro.com>
Dear Mark Brown,
> On Fri, Oct 26, 2012 at 02:31:53PM +0200, Marek Vasut wrote:
> > Dear Mark Brown,
> >
> > > Applied both, thanks.
> >
> > Will they hit 3.7 please?
>
> I hadn't been going to do that, no - nothing about them seemed
> especially urgent?
They're fixes, I'd be glad if you could slip them in. They're not urgent, but
it'd be nice to have them included. Esp. since 3.7 seems like a really _good_
kernel for MXS, I'd love to have everything nicely polished in it.
Best regards,
Marek Vasut
prev parent reply other threads:[~2012-10-26 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 2:32 [PATCH 1/2] spi: mxs: Assign message status after transfer finished Marek Vasut
2012-10-14 2:32 ` [PATCH 2/2] spi: mxs: Terminate DMA in case of DMA timeout Marek Vasut
2012-10-17 7:10 ` [PATCH 1/2] spi: mxs: Assign message status after transfer finished Mark Brown
2012-10-26 12:31 ` Marek Vasut
2012-10-26 13:05 ` Mark Brown
2012-10-26 13:13 ` Marek Vasut [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=201210261513.47664.marex@denx.de \
--to=marex@denx.de \
--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).