From: Schrempf Frieder <frieder.schrempf@kontron.de>
To: Mark Brown <broonie@kernel.org>
Cc: Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com>,
"bbrezillon@kernel.org" <bbrezillon@kernel.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>
Subject: Re: [PATCH] spi: spi-mem: spi-fsl-qspi: typo fix in author name
Date: Tue, 29 Jan 2019 12:08:26 +0000 [thread overview]
Message-ID: <24c8ce00-5a7c-cec0-df5b-fca6e13bccb0@kontron.de> (raw)
In-Reply-To: <20190129115937.GB10524@sirena.org.uk>
On 29.01.19 12:59, Mark Brown wrote:
> On Tue, Jan 29, 2019 at 11:46:02AM +0000, Schrempf Frieder wrote:
>
>> Mark, could you please squash this with the original commit
>> (84d043185dbe spi: Add a driver for the Freescale/NXP QuadSPI
>> controller) in spi-next?
>
> That'd mean a rebase unfortunately.
Ah, ok no problem. Then please just apply it with:
Fixes: 84d043185dbe ("spi: Add a driver for the Freescale/NXP QuadSPI
controller")
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-01-29 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 9:55 [PATCH] spi: spi-mem: spi-fsl-qspi: typo fix in author name Yogesh Narayan Gaur
2019-01-29 11:46 ` Schrempf Frieder
2019-01-29 11:59 ` Mark Brown
2019-01-29 12:08 ` Schrempf Frieder [this message]
2019-01-29 12:12 ` Mark Brown
2019-01-29 12:14 ` Applied "spi: spi-mem: spi-fsl-qspi: typo fix in author name" to the spi tree Mark Brown
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=24c8ce00-5a7c-cec0-df5b-fca6e13bccb0@kontron.de \
--to=frieder.schrempf@kontron.de \
--cc=bbrezillon@kernel.org \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=yogeshnarayan.gaur@nxp.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).