From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6] ARM: sun4i: spi: Allow transfers larger than FIFO size
Date: Thu, 21 Jul 2016 19:20:37 +0100 [thread overview]
Message-ID: <20160721182037.GQ6509@sirena.org.uk> (raw)
In-Reply-To: <20160721172712.GA10640@weiser.dinsnail.net>
On Thu, Jul 21, 2016 at 07:27:12PM +0200, Michael Weiser wrote:
> On Thu, Jul 21, 2016 at 05:31:53PM +0100, Mark Brown wrote:
> > > What is keeping the patch from being merged (i.e. into mainline)?
> > Someone needs to address whatever review comments there were on the last
> > version and submit it.
> That's my point: There don't seem to be any.
> v6 was resend with fixes to checkpatch niggles on v5:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-August/363073.html
I can't tell if that was even submitted, it's got a subject line of
"ARM: sun4i" so there's every chance that even if it was sent to me it
got deleted unread. Whatever was going on it needs to be submited.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160721/23a291e2/attachment.sig>
prev parent reply other threads:[~2016-07-21 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 19:41 [PATCH v6] ARM: sun4i: spi: Allow transfers larger than FIFO size Olliver Schinagl
2015-08-08 19:41 ` Olliver Schinagl
2016-07-21 11:27 ` Michael Weiser
2016-07-21 16:31 ` Mark Brown
2016-07-21 17:27 ` Michael Weiser
[not found] ` <34E27D10-C620-4288-A1A8-489B75D4757B@schinagl.nl>
2016-07-21 18:15 ` Mark Brown
2016-07-21 18:20 ` 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=20160721182037.GQ6509@sirena.org.uk \
--to=broonie@kernel.org \
--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).