From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, Mason Yang <masonccyang@mxic.com.tw>,
linux-renesas-soc@vger.kernel.org,
Chris Brandt <chris.brandt@renesas.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v4] spi: add Renesas RPC-IF driver
Date: Tue, 16 Jun 2020 15:55:24 +0300 [thread overview]
Message-ID: <48df1997-31d8-06b4-7fce-a3b9b5cfaac8@cogentembedded.com> (raw)
In-Reply-To: <20200616093404.GH4447@sirena.org.uk>
On 16.06.2020 12:34, Mark Brown wrote:
>>>> 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
>
>> No. I thought we had an agreement about this (core) driver going in thru
>> the SPI tree (because there's no repo for drivers/memory/ anyway). Looking
>> at the DT patchwork:
>
>> https://patchwork.ozlabs.org/project/devicetree-bindings/patch/4becbd3b-c9b9-070a-5771-48cade6651e5@cogentembedded.com/
>
> Nobody appears to have ever actually sent me these to me so they're not
> getting applied...
Ah, you need to be explicitly CCed! I seem to be relying on the patchwork
too much... OK, I'm going for v5 of the core driver/bindings later today (with
r8a77970 added to compatibles -- I tested it yesterday).
>> the DT bindings still need to be reviewed -- but by whom? The "Checks"
>> section indicates that they did pass the DT checks this time around).
>> Rob?
>
> There's a backlog on YAML binding reviews, I'm sure Rob will get to it
> in time.
>>> the patch, no feedback for months on the patch and I've not seen any
>>> ongoing discussion.
>
>> Everybody seems to be in a silent agreement. :-)
>
> Or lost track of things given how long this has been going on :(
Sorry, there was a lat of hardware issues slowing me down. :-(
MBR, Sergei
next prev parent reply other threads:[~2020-06-16 12:55 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
2020-06-16 8:48 ` Sergei Shtylyov
2020-06-16 9:34 ` Mark Brown
2020-06-16 12:55 ` Sergei Shtylyov [this message]
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=48df1997-31d8-06b4-7fce-a3b9b5cfaac8@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=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=robh+dt@kernel.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