From: Mark Brown <broonie@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Marek Vasut <marex@denx.de>,
linux-spi@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
kernel@pengutronix.de, Robin Gong <yibin.gong@nxp.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/5] spi: imx: Fix polarity switching for mx51-ecspi
Date: Wed, 12 Dec 2018 09:21:48 +0000 [thread overview]
Message-ID: <20181212092148.GA6920@sirena.org.uk> (raw)
In-Reply-To: <20181211204047.GR6686@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1063 bytes --]
On Tue, Dec 11, 2018 at 08:40:47PM +0000, Mark Brown wrote:
> On Tue, Dec 11, 2018 at 09:11:26PM +0100, Uwe Kleine-König wrote:
> > FTR: your reference to an "unanswered question" wasn't optimal either. I
> > had to search my inbox for a while to determine what you could have
> > meant :-)
> At the time I wrote that I didn't actually know, I just knew that I'd
> remembered the subthread ended with a question to Marek about if this
> was needed.
Just to expand on this a bit: the way I'm working here is that I'm
remembering if there's some reason I'm expecting some additional
replies, either because there's someone likely to do review on the
relevant code, there was some specific question I remember or because
there was a discussion that seemed to peter out without conclusion
between people who are likely to respond. If something like that is
happening I'll leave a bit longer for replies than I might otherwise
(conversely if it's something where it's very unlikely that there will
be any comment I'll tend to leave less time).
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-12-12 9:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 6:47 [PATCH v3 0/5] spi: imx: Fix polarity switching for mx51-ecspi Uwe Kleine-König
2018-11-30 6:47 ` [PATCH v3 1/5] spi: imx: add a device specific prepare_message callback Uwe Kleine-König
2018-11-30 6:47 ` [PATCH v3 2/5] spi: imx: mx51-ecspi: Move some initialisation to prepare_message hook Uwe Kleine-König
2018-12-03 8:00 ` Robin Gong
2018-12-03 8:18 ` Uwe Kleine-König
2018-11-30 6:47 ` [PATCH v3 3/5] spi: imx: style fixes Uwe Kleine-König
2018-11-30 6:47 ` [PATCH v3 4/5] spi: imx: rename config callback and add useful parameters Uwe Kleine-König
2018-12-03 8:09 ` Robin Gong
2018-12-03 8:29 ` Uwe Kleine-König
2018-11-30 6:47 ` [PATCH v3 5/5] spi: imx: drop useless member speed_hz from driver data struct Uwe Kleine-König
2018-11-30 17:21 ` Trent Piepho
2018-11-30 17:50 ` Uwe Kleine-König
2018-11-30 18:10 ` Trent Piepho
2018-11-30 18:21 ` Uwe Kleine-König
2018-12-10 21:52 ` [PATCH v3 0/5] spi: imx: Fix polarity switching for mx51-ecspi Uwe Kleine-König
2018-12-11 1:14 ` Mark Brown
2018-12-11 7:13 ` Uwe Kleine-König
2018-12-11 11:56 ` Mark Brown
2018-12-11 20:11 ` Uwe Kleine-König
2018-12-11 20:40 ` Mark Brown
2018-12-12 9:21 ` 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=20181212092148.GA6920@sirena.org.uk \
--to=broonie@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-spi@vger.kernel.org \
--cc=marex@denx.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=yibin.gong@nxp.com \
/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).