From: Wolfram Sang <wsa@the-dreams.de>
To: Mark Brown <broonie@kernel.org>
Cc: Ulrich Hecht <uli+renesas@fpond.eu>,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
geert@linux-m68k.org, linux-spi@vger.kernel.org
Subject: Re: [RESEND PATCH] spi: sh-msiof: Document R-Car D3 support
Date: Tue, 4 Sep 2018 09:20:17 +0200 [thread overview]
Message-ID: <20180904072017.GA996@kunai> (raw)
In-Reply-To: <20180903110219.GB10302@sirena.org.uk>
[-- 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 --]
next prev parent reply other threads:[~2018-09-04 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2018-09-04 7:29 ` Ulrich Hecht
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=20180904072017.GA996@kunai \
--to=wsa@the-dreams.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=uli+renesas@fpond.eu \
/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).