* [RESEND PATCH] spi: sh-msiof: Document R-Car D3 support
@ 2018-08-24 9:12 Ulrich Hecht
2018-09-03 9:28 ` Wolfram Sang
0 siblings, 1 reply; 5+ messages in thread
From: Ulrich Hecht @ 2018-08-24 9:12 UTC (permalink / raw)
To: devicetree; +Cc: linux-renesas-soc, wsa, geert, linux-spi, Ulrich Hecht
Document support for the MSIOF module in the Renesas D3 (r8a77995) SoC.
No driver update is needed.
Signed-off-by: Ulrich Hecht <uli+renesas@fpond.eu>
Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
This patch fell by the wayside, probably because I forgot to cc devicetree.
CU
Uli
Documentation/devicetree/bindings/spi/sh-msiof.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/sh-msiof.txt b/Documentation/devicetree/bindings/spi/sh-msiof.txt
index bfbc203..fd15715 100644
--- a/Documentation/devicetree/bindings/spi/sh-msiof.txt
+++ b/Documentation/devicetree/bindings/spi/sh-msiof.txt
@@ -11,6 +11,7 @@ Required properties:
"renesas,msiof-r8a7795" (R-Car H3)
"renesas,msiof-r8a7796" (R-Car M3-W)
"renesas,msiof-r8a77965" (R-Car M3-N)
+ "renesas,msiof-r8a77995" (R-Car D3)
"renesas,msiof-sh73a0" (SH-Mobile AG5)
"renesas,sh-mobile-msiof" (generic SH-Mobile compatibile device)
"renesas,rcar-gen2-msiof" (generic R-Car Gen2 and RZ/G1 compatible device)
--
2.7.4
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [RESEND PATCH] spi: sh-msiof: Document R-Car D3 support
2018-08-24 9:12 [RESEND PATCH] spi: sh-msiof: Document R-Car D3 support Ulrich Hecht
@ 2018-09-03 9:28 ` Wolfram Sang
2018-09-03 11:02 ` Mark Brown
0 siblings, 1 reply; 5+ messages in thread
From: Wolfram Sang @ 2018-09-03 9:28 UTC (permalink / raw)
To: Ulrich Hecht, Mark Brown; +Cc: devicetree, linux-renesas-soc, geert, linux-spi
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
On Fri, Aug 24, 2018 at 11:12:31AM +0200, Ulrich Hecht wrote:
> Document support for the MSIOF module in the Renesas D3 (r8a77995) SoC.
>
> No driver update is needed.
>
> Signed-off-by: Ulrich Hecht <uli+renesas@fpond.eu>
> Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> This patch fell by the wayside, probably because I forgot to cc devicetree.
Yeah, this is good practice. Yet, I'd think this goes upstream via the
SPI tree? Ccing Mark, he prefers to be Cced explicitly.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [RESEND PATCH] spi: sh-msiof: Document R-Car D3 support
2018-09-03 9:28 ` Wolfram Sang
@ 2018-09-03 11:02 ` Mark Brown
2018-09-04 7:20 ` Wolfram Sang
0 siblings, 1 reply; 5+ messages in thread
From: Mark Brown @ 2018-09-03 11:02 UTC (permalink / raw)
To: Wolfram Sang
Cc: Ulrich Hecht, devicetree, linux-renesas-soc, geert, linux-spi
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On Mon, Sep 03, 2018 at 11:28:19AM +0200, Wolfram Sang wrote:
> On Fri, Aug 24, 2018 at 11:12:31AM +0200, Ulrich Hecht wrote:
> > This patch fell by the wayside, probably because I forgot to cc devicetree.
> Yeah, this is good practice. Yet, I'd think this goes upstream via the
> SPI tree? Ccing Mark, he prefers to be Cced explicitly.
Yes, if I don't get sent a copy of patches I'm not going to see them:
As documented in SubmittingPatches please send patches to the
maintainers for the code you would like to change. The normal kernel
workflow is that people apply patches from their inboxes, if they aren't
copied they are likely to not see the patch at all and it is much more
difficult to apply patches.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [RESEND PATCH] spi: sh-msiof: Document R-Car D3 support
2018-09-03 11:02 ` Mark Brown
@ 2018-09-04 7:20 ` Wolfram Sang
2018-09-04 7:29 ` Ulrich Hecht
0 siblings, 1 reply; 5+ messages in thread
From: Wolfram Sang @ 2018-09-04 7:20 UTC (permalink / raw)
To: Mark Brown; +Cc: Ulrich Hecht, devicetree, linux-renesas-soc, geert, linux-spi
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
On Mon, Sep 03, 2018 at 12:02:19PM +0100, Mark Brown wrote:
> On Mon, Sep 03, 2018 at 11:28:19AM +0200, Wolfram Sang wrote:
> > On Fri, Aug 24, 2018 at 11:12:31AM +0200, Ulrich Hecht wrote:
>
> > > This patch fell by the wayside, probably because I forgot to cc devicetree.
>
> > Yeah, this is good practice. Yet, I'd think this goes upstream via the
> > SPI tree? Ccing Mark, he prefers to be Cced explicitly.
>
> Yes, if I don't get sent a copy of patches I'm not going to see them:
>
> As documented in SubmittingPatches please send patches to the
> maintainers for the code you would like to change. The normal kernel
> workflow is that people apply patches from their inboxes, if they aren't
> copied they are likely to not see the patch at all and it is much more
> difficult to apply patches.
Uli, can you resend?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [RESEND PATCH] spi: sh-msiof: Document R-Car D3 support
2018-09-04 7:20 ` Wolfram Sang
@ 2018-09-04 7:29 ` Ulrich Hecht
0 siblings, 0 replies; 5+ messages in thread
From: Ulrich Hecht @ 2018-09-04 7:29 UTC (permalink / raw)
To: Wolfram Sang, Mark Brown
Cc: Ulrich Hecht, devicetree, linux-renesas-soc, geert, linux-spi
> On September 4, 2018 at 9:20 AM Wolfram Sang <wsa@the-dreams.de> wrote:
>
>
> On Mon, Sep 03, 2018 at 12:02:19PM +0100, Mark Brown wrote:
> > On Mon, Sep 03, 2018 at 11:28:19AM +0200, Wolfram Sang wrote:
> > > On Fri, Aug 24, 2018 at 11:12:31AM +0200, Ulrich Hecht wrote:
> >
> > > > This patch fell by the wayside, probably because I forgot to cc devicetree.
> >
> > > Yeah, this is good practice. Yet, I'd think this goes upstream via the
> > > SPI tree? Ccing Mark, he prefers to be Cced explicitly.
> >
> > Yes, if I don't get sent a copy of patches I'm not going to see them:
> >
> > As documented in SubmittingPatches please send patches to the
> > maintainers for the code you would like to change. The normal kernel
> > workflow is that people apply patches from their inboxes, if they aren't
> > copied they are likely to not see the patch at all and it is much more
> > difficult to apply patches.
>
> Uli, can you resend?
Geert has already done so, together with the corresponding change for E3.
CU
Uli
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2018-09-04 12:05 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-08-24 9:12 [RESEND PATCH] spi: sh-msiof: Document R-Car D3 support Ulrich Hecht
2018-09-03 9:28 ` Wolfram Sang
2018-09-03 11:02 ` Mark Brown
2018-09-04 7:20 ` Wolfram Sang
2018-09-04 7:29 ` Ulrich Hecht
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.