All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Hecht <uli@fpond.eu>
To: Wolfram Sang <wsa@the-dreams.de>, 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:29:24 +0200 (CEST)	[thread overview]
Message-ID: <1827947028.947358.1536046165147@webmail.strato.com> (raw)
In-Reply-To: <20180904072017.GA996@kunai>


> 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

      reply	other threads:[~2018-09-04 12:05 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
2018-09-04  7:29       ` Ulrich Hecht [this message]

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=1827947028.947358.1536046165147@webmail.strato.com \
    --to=uli@fpond.eu \
    --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 \
    --cc=wsa@the-dreams.de \
    /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 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.