From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Subject: Re: [PATCH] spi/imx: Add MAINTAINERS entry for i.MX SPI driver
Date: Tue, 16 Sep 2014 18:12:28 +0200 [thread overview]
Message-ID: <201409161812.28216.marex@denx.de> (raw)
In-Reply-To: <20140916160557.GL7960-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On Tuesday, September 16, 2014 at 06:05:57 PM, Mark Brown wrote:
> On Tue, Sep 16, 2014 at 07:13:17AM +0200, Marek Vasut wrote:
> > git log --follow tells me you have it wrong. I wrote the MXS one ;-)
> >
> > commit b5f3294f0be5496aec01e5aa709a5fab8bb2f225
> > Author: Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
> > Date: Tue Sep 22 16:46:02 2009 -0700
> >
> > spi: add SPI driver for most known i.MX SoCs
>
> Gah, sorry.
No problem. I'm happy to help reviewing the iMX ones too as it concerns me as
well, but let's keep the credit straight ;-)
Best regards,
Marek Vasut
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-09-16 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 22:44 [PATCH] spi/imx: Add MAINTAINERS entry for i.MX SPI driver Mark Brown
[not found] ` <1410821060-9102-1-git-send-email-broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2014-09-16 5:13 ` Marek Vasut
[not found] ` <201409160713.17273.marex-ynQEQJNshbs@public.gmane.org>
2014-09-16 16:05 ` Mark Brown
[not found] ` <20140916160557.GL7960-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-09-16 16:12 ` Marek Vasut [this message]
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=201409161812.28216.marex@denx.de \
--to=marex-ynqeqjnshbs@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
/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).