From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Mark Brown <broonie@kernel.org>, linux-spi@vger.kernel.org
Cc: 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 11:24:55 +0300 [thread overview]
Message-ID: <6fd4533e-c548-5d14-2d21-96efa0c58a0b@cogentembedded.com> (raw)
In-Reply-To: <159226448570.27735.17453498854310254061.b4-ty@kernel.org>
On 16.06.2020 2:41, Mark Brown wrote:
>> Add the SPI driver for the Renesas RPC-IF. It's the "front end" driver
>> using the "back end" APIs in the main driver to talk to the real hardware.
>> We only implement the 'spi-mem' interface -- there's no need to implement
>> the usual SPI driver methods...
>>
>> Based on the original patch by Mason Yang <masonccyang@mxic.com.tw>.
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
>
> Thanks!
>
> [1/1] spi: add Renesas RPC-IF driver
> commit: eb8d6d464a27850498dced21a8450e85d4a02009
>
> 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?
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
>
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
>
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
>
> Thanks,
> Mark
MBR, Sergei
next prev parent reply other threads:[~2020-06-16 8:25 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 [this message]
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
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=6fd4533e-c548-5d14-2d21-96efa0c58a0b@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 \
/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).