From: Mark Brown <broonie@kernel.org>
To: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Trent Piepho <tpiepho@impinj.com>
Subject: Re: [PATCH v3] spi: dw: support 4-16 bits per word
Date: Thu, 6 Sep 2018 14:23:33 +0100 [thread overview]
Message-ID: <20180906132333.GG5360@sirena.org.uk> (raw)
In-Reply-To: <CAAh8qsyMcL-acBf4nXq2RSE=Y43FMG8v+TuyvvmgGtkjHchAyQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Thu, Sep 06, 2018 at 01:23:34PM +0200, Simon Goldschmidt wrote:
> On Thu, Sep 6, 2018 at 1:09 PM Mark Brown <broonie@kernel.org> wrote:
> > Please don't send new patches in reply to old patch serieses, it makes
> > it harder to follow what the current version of things is and makes it
> > much easier for the patches to get lost in the old threads.
> Ok, no problem and thanks for the hint! Where does this requirement
> come from? Patchwork or mail sorting habits?
Mail sorting. It can mean that you get things like someone deleting a
thread and the new patch getting caught up in a thread delete command
and hence missed.
> Anyway, how does this continue, will you pick the patch or do I need
> to somehow collect yet more reviews?
You should've got a mail at about the same time saying it's been
applied.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-09-06 13:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 7:14 [PATCH] spi: dw: support 4-16 bits per word Simon Goldschmidt
2018-08-08 9:45 ` Andy Shevchenko
2018-08-08 11:58 ` Simon Goldschmidt
2018-08-08 12:26 ` Andy Shevchenko
2018-08-17 7:01 ` [PATCH v2] " Simon Goldschmidt
2018-08-17 11:17 ` Andy Shevchenko
2018-08-17 16:32 ` Trent Piepho
2018-08-18 8:37 ` Simon Goldschmidt
2018-09-04 19:49 ` [PATCH v3] " Simon Goldschmidt
2018-09-06 11:09 ` Mark Brown
2018-09-06 11:23 ` Simon Goldschmidt
2018-09-06 13:23 ` Mark Brown [this message]
2018-09-06 13:37 ` Simon Goldschmidt
2018-09-06 11:10 ` Applied "spi: dw: support 4-16 bits per word" to the spi tree Mark Brown
2018-09-06 11:10 ` 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=20180906132333.GG5360@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=simon.k.r.goldschmidt@gmail.com \
--cc=tpiepho@impinj.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.