From: Mark Brown <broonie@kernel.org>
To: Lukasz Majewski <lukma@denx.de>
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 11:57:37 +0100 [thread overview]
Message-ID: <20190204105737.GE23441@sirena.org.uk> (raw)
In-Reply-To: <20190204113001.77d59570@jawa>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-04 10:57 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 [this message]
2019-02-04 12:52 ` Lukasz Majewski
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=20190204105737.GE23441@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andrew.smirnov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=eha@deif.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lukma@denx.de \
--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).