From: Mark Brown <firstname.lastname@example.org> To: Lukasz Majewski <email@example.com> Cc: "Mark Rutland" <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, "Esben Haabendal" <firstname.lastname@example.org>, "Martin Hundebøll" <email@example.com>, "Andrey Smirnov" <firstname.lastname@example.org> Subject: Re: [PATCH v5] ARM: dspi: Provide support for DSPI slave mode operation (Vybryd vf610) Date: Mon, 4 Feb 2019 14:03:56 +0100 [thread overview] Message-ID: <20190204130356.GF23441@sirena.org.uk> (raw) In-Reply-To: <20190204135242.7112d48c@jawa> [-- Attachment #1: Type: text/plain, Size: 1180 bytes --] 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. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-04 13:04 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 " 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 2019-02-04 13:03 ` Mark Brown [this message] 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=20190204130356.GF23441@sirena.org.uk \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v5] ARM: dspi: Provide support for DSPI slave mode operation (Vybryd vf610)' \ /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
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).