From: Mark Brown <broonie@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
linux-kernel@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Sascha Weisenberger <sascha.weisenberger@siemens.com>
Subject: Re: [PATCH v3 2/3] spi: pxa2xx: Prepare for edge-triggered interrupts
Date: Fri, 20 Jan 2017 12:21:29 +0000 [thread overview]
Message-ID: <20170120122129.6cn5phrobeldpikp@sirena.org.uk> (raw)
In-Reply-To: <1484856272.2133.253.camel@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
On Thu, Jan 19, 2017 at 10:04:32PM +0200, Andy Shevchenko wrote:
> On Thu, 2017-01-19 at 19:57 +0000, Mark Brown wrote:
> > I'm missing patches 1 and 3, what's going on here?
> Patch 1 had been applied by you. I think Jan just needs to resend with
> proper version and set of patches.
OK - Jan, the purpose of numbering patches in a series is so we can tell
what order they come in. That's it. If the set of patches gets changed
due to things being added or removed the numbers will be different but
that's totally OK as their only relevance is in ordering things within a
given posting.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-01-20 12:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 18:44 [PATCH v2 0/3] spi: pca2xx: Prepare for and enable MSI support Jan Kiszka
2017-01-16 18:44 ` [PATCH v2 1/3] spi: pxa2xx: Factor out handle_bad_msg Jan Kiszka
2017-01-17 11:18 ` Jarkko Nikula
2017-01-17 18:46 ` Applied "spi: pxa2xx: Factor out handle_bad_msg" to the spi tree Mark Brown
2017-01-16 18:44 ` [PATCH v2 2/3] spi: pxa2xx: Prepare for edge-triggered interrupts Jan Kiszka
2017-01-16 19:07 ` Andy Shevchenko
2017-01-16 19:46 ` Jan Kiszka
2017-01-17 18:52 ` Jan Kiszka
2017-01-17 7:54 ` Robert Jarzmik
2017-01-17 8:05 ` Jan Kiszka
2017-01-18 8:21 ` Robert Jarzmik
2017-01-18 9:33 ` Jan Kiszka
2017-01-18 12:46 ` Mark Brown
2017-01-19 15:34 ` Jan Kiszka
2017-01-19 19:37 ` [PATCH v3 " Jan Kiszka
2017-01-19 19:57 ` Mark Brown
2017-01-19 20:04 ` Andy Shevchenko
2017-01-20 12:21 ` Mark Brown [this message]
2017-01-20 15:29 ` Jan Kiszka
2017-01-20 16:14 ` Mark Brown
2017-01-20 7:42 ` Robert Jarzmik
2017-01-24 18:39 ` Applied "spi: pxa2xx: Prepare for edge-triggered interrupts" to the spi tree Mark Brown
2017-01-17 7:58 ` [PATCH v2 2/3] spi: pxa2xx: Prepare for edge-triggered interrupts Robert Jarzmik
2017-01-17 8:10 ` Jan Kiszka
2017-01-17 13:11 ` Jarkko Nikula
2017-01-17 14:43 ` Jan Kiszka
2017-01-16 18:44 ` [PATCH v2 3/3] spi: pca2xx-pci: Allow MSI Jan Kiszka
2017-01-16 19:08 ` Andy Shevchenko
2017-01-17 11:18 ` Jarkko Nikula
2017-01-24 18:39 ` Applied "spi: pca2xx-pci: Allow MSI" to the spi tree Mark Brown
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=20170120122129.6cn5phrobeldpikp@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=robert.jarzmik@free.fr \
--cc=sascha.weisenberger@siemens.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).