[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190204130356.GF23441@sirena.org.uk>
Date: Mon, 4 Feb 2019 14:03:56 +0100
From: Mark Brown <broonie@...nel.org>
To: Lukasz Majewski <lukma@...x.de>
Cc: Mark Rutland <mark.rutland@....com>, linux-spi@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Esben Haabendal <eha@...f.com>,
Martin Hundebøll <martin@...nix.com>,
Andrey Smirnov <andrew.smirnov@...il.com>
Subject: Re: [PATCH v5] ARM: dspi: Provide support for DSPI slave mode
operation (Vybryd vf610)
On Mon, Feb 04, 2019 at 01:52:42PM +0100, Lukasz Majewski wrote:
> > On Mon, Feb 04, 2019 at 11:30:01AM +0100, Lukasz Majewski wrote:
> > You've been sending ARM: patches to me (the SPI maintainer) and one of
> > the DT maintainers.
...
> 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.
If they're SPI patches they should have a changelog that looks like a
SPI patch which means that it should start with "spi" (see other patches
on the list or git log for examples). When your patch subject lines
start with ARM: that means they are for arch/arm - I don't 100% know but
I suspect I've just not got far enough into the mails to notice that
they're for SPI, people do send a lot of patches that just happen to
mention buses to maintainers for those buses. In general you should try
to make sure that the subject line for your patch matches the style used
in the relevant subsystem.
> What else shall I do?
You'll need to resend the patch, preferrably with a suitable subject
line.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists