linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Mark Brown <broonie@kernel.org>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
	linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Esben Haabendal" <eha@deif.com>,
	"Martin Hundebøll" <martin@geanix.com>,
	"Andrey Smirnov" <andrew.smirnov@gmail.com>
Subject: Re: [PATCH v5] ARM: dspi: Provide support for DSPI slave mode operation (Vybryd vf610)
Date: Mon, 4 Feb 2019 13:52:42 +0100	[thread overview]
Message-ID: <20190204135242.7112d48c@jawa> (raw)
In-Reply-To: <20190204105737.GE23441@sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]

Hi Mark,

> On Mon, Feb 04, 2019 at 11:30:01AM +0100, Lukasz Majewski wrote:
> 
> > Is there any interest in adding new code (or fixes) to VF610 ?   
> 
> You've been sending ARM: patches to me (the SPI maintainer) and one of
> the DT maintainers. 
> You need to send patches for that platform to the
> relevant platform maintainers, I only maintain drivers/spi (and some
> other subsystems).  Similarly the DT maintainers only maintain the
> generic devicetree stuff (but apply relatively few patches directly).
> 
> Please see submitting-patches.rst for details.

https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html
Point 5):

git format-patch -1 e26e01ac03aae6cf296e7b4de47354d3151b21e7
0001-ARM-dspi-Provide-support-for-DSPI-slave-mode-operati.patch

./scripts/get_maintainer.pl
0001-ARM-dspi-Provide-support-for-DSPI-slave-mode-operati.patch Mark
Brown <broonie@kernel.org> (maintainer:SPI SUBSYSTEM)
linux-spi@vger.kernel.org (open list:SPI SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)

Moreover, I've CC'ed developers (Esben, Andrey, Martin) involved in the
changes for previous work done in this file/driver.

And those changes are solely related to SPI work in this driver, no ARM
Vybrid.

What else shall I do?


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-02-04 12:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 15:07 [PATCH v2] ARM: dspi: Provide support for DSPI slave more operation (Vybryd vf610) Lukasz Majewski
2018-10-08 12:23 ` Lukasz Majewski
2018-10-23  9:13 ` [RESEND PATCHv2] " Lukasz Majewski
2018-11-13 12:06 ` [PATCHv3] ARM: dspi: Provide support for DSPI slave mode " Lukasz Majewski
2018-12-02  8:47   ` Lukasz Majewski
2018-12-09 21:57 ` [PATCHv4] " Lukasz Majewski
2019-01-09  8:26 ` [PATCH v5] " Lukasz Majewski
2019-02-04 10:30   ` Lukasz Majewski
2019-02-04 10:57     ` Mark Brown
2019-02-04 12:52       ` Lukasz Majewski [this message]
2019-02-04 13:03         ` Mark Brown
2019-02-04 13:12           ` Lukasz Majewski
2019-02-05 22:13 ` [PATCH v6] spi: spi-fsl-dspi: " Lukasz Majewski

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=20190204135242.7112d48c@jawa \
    --to=lukma@denx.de \
    --cc=andrew.smirnov@gmail.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eha@deif.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=martin@geanix.com \
    /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).