From: Mark Brown <broonie@kernel.org>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: linux-spi@vger.kernel.org, Mason Yang <masonccyang@mxic.com.tw>,
linux-renesas-soc@vger.kernel.org,
Chris Brandt <chris.brandt@renesas.com>
Subject: Re: [PATCH v4] spi: add Renesas RPC-IF driver
Date: Tue, 16 Jun 2020 09:38:56 +0100 [thread overview]
Message-ID: <20200616083856.GF4447@sirena.org.uk> (raw)
In-Reply-To: <6fd4533e-c548-5d14-2d21-96efa0c58a0b@cogentembedded.com>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
On Tue, Jun 16, 2020 at 11:24:55AM +0300, Sergei Shtylyov wrote:
> On 16.06.2020 2:41, Mark Brown wrote:
> > All being well this means that it will be integrated into the linux-next
> > tree (usually sometime in the next 24 hours) and sent to Linus during
> > the next merge window (or sooner if it is a bug fix), however if
> > problems are discovered then the patch may be dropped or reverted.
> You realize that the SPI driver won't build alone, w/o the
> drivers/memory/ core driver merged, right?
Those aren't merged yet? There was no mention of any dependencies in
the patch, no feedback for months on the patch and I've not seen any
ongoing discussion.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-16 8:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ad503d6e-4739-9744-64b4-fd13f44ea6fe@cogentembedded.com>
[not found] ` <ad503d6e-4739-9744-64b4-fd13f44ea6fe-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2020-01-15 20:46 ` [PATCH v2] spi: add Renesas RPC-IF driver Sergei Shtylyov
[not found] ` <6515c5ec-8432-0b20-426d-0428bbdf3712-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2020-02-07 22:36 ` Chris Brandt
[not found] ` <TY1PR01MB1562509AEBD0B4460D3FEC798A1C0-5SGCI54O2uKy/kJTUOSl63colHNk5qUtvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2020-02-10 18:43 ` Sergei Shtylyov
2020-02-10 18:06 ` Chris Brandt
[not found] ` <TYXPR01MB1568E8BCB6B80A77C91D98998A190-enDngAEzY3rnUoU5SHyUhXcolHNk5qUtvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2020-02-10 19:34 ` Chris Brandt
2020-05-08 19:54 ` [PATCH v3] " Sergei Shtylyov
2020-06-13 19:18 ` [PATCH v4] " Sergei Shtylyov
2020-06-15 23:41 ` Mark Brown
2020-06-16 8:24 ` Sergei Shtylyov
2020-06-16 8:38 ` Mark Brown [this message]
2020-06-16 8:48 ` Sergei Shtylyov
2020-06-16 9:34 ` Mark Brown
2020-06-16 12:55 ` Sergei Shtylyov
2020-06-16 14:32 ` Mark Brown
2020-06-16 9:26 ` Sergei Shtylyov
2020-06-16 9:34 ` 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=20200616083856.GF4447@sirena.org.uk \
--to=broonie@kernel.org \
--cc=chris.brandt@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=masonccyang@mxic.com.tw \
--cc=sergei.shtylyov@cogentembedded.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