linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: Mark Brown <broonie-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	attila-HB9FjVmMKa7tRgLqZ5aouw@public.gmane.org
Subject: Re: [PATCH 00/10] MXS SPI driver
Date: Wed, 18 Jul 2012 15:37:52 +0200	[thread overview]
Message-ID: <201207181537.52610.marex@denx.de> (raw)
In-Reply-To: <20120718111049.GA9923-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>

Dear Mark Brown,

> On Wed, Jul 18, 2012 at 12:09:54AM +0200, Marek Vasut wrote:
> > > On Mon, Jul 16, 2012 at 02:09:47PM +0200, Marek Vasut wrote:
> > > 
> > > Always CC maintainers, and in this case me as well (I'm collecting SPI
> > > patches for this release since Grant's mostly offline).
> > 
> > Ah, I wasn't aware you're the SPI maintainer now. Sorry about that. Will
> > do if there's a rework requested.
> 
> I'm not, I'm just looking after things for this release (until Grant's
> finished moving house and attending conferences).

Roger that, thanks for helping me.

I'll add you the the CC when I'll roll out the updated series, fixing the issue 
pointed out by Attila. I believe Shawn and Dong are CCed, which are the MXS 
(imx23/imx28) maintainers. Who else should be CCed?

Did you notice any other problems please?

Best regards,
Marek Vasut

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

      parent reply	other threads:[~2012-07-18 13:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 12:09 [PATCH 00/10] MXS SPI driver Marek Vasut
     [not found] ` <1342440597-8395-1-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
2012-07-16 12:09   ` [PATCH 01/10] mmc: spi: Move SSP register definitions into separate file Marek Vasut
2012-07-16 12:09   ` [PATCH 02/10] mmc: spi: Rename IMX2[38]_MMC to IMX2[38]_SSP Marek Vasut
2012-07-16 12:09   ` [PATCH 03/10] mmc: spi: Add necessary bits into mxs-spi.h Marek Vasut
2012-07-16 12:09   ` [PATCH 04/10] mmc: spi: Pull out parts shared between MMC and SPI Marek Vasut
2012-07-16 12:09   ` [PATCH 05/10] mmc: spi: Pull out the SSP clock configuration function Marek Vasut
     [not found]     ` <1342440597-8395-6-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
2012-07-17 13:39       ` Attila Kinali
     [not found]         ` <20120717153901.5530a246a7a5fecfef03b373-HB9FjVmMKa7tRgLqZ5aouw@public.gmane.org>
2012-07-17 21:48           ` Marek Vasut
     [not found]             ` <201207172348.34919.marex-ynQEQJNshbs@public.gmane.org>
2012-07-18  6:07               ` Attila Kinali
     [not found]                 ` <20120718080755.cf7d4ac2e423278ce12843e6-HB9FjVmMKa7tRgLqZ5aouw@public.gmane.org>
2012-07-18  8:40                   ` Marek Vasut
2012-07-16 12:09   ` [PATCH 06/10] spi: Add SPI driver for mx233/mx28 Marek Vasut
2012-07-16 12:09   ` [PATCH 07/10] mmc: spi: Pull out common DMA parts from MXS MMC Marek Vasut
2012-07-16 12:09   ` [PATCH 08/10] spi: Add DMA support into SPI driver Marek Vasut
2012-07-16 12:09   ` [PATCH 09/10] spi: Add SSP/SPI device tree documentation Marek Vasut
2012-07-16 12:09   ` [PATCH 10/10] ARM: mx28: Add SPI pinmux into imx28.dtsi Marek Vasut
2012-07-17 15:31   ` [PATCH 00/10] MXS SPI driver Mark Brown
     [not found]     ` <20120717153110.GC3107-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-07-17 22:09       ` Marek Vasut
     [not found]         ` <201207180009.54189.marex-ynQEQJNshbs@public.gmane.org>
2012-07-18 11:10           ` Mark Brown
     [not found]             ` <20120718111049.GA9923-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-07-18 13:37               ` 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=201207181537.52610.marex@denx.de \
    --to=marex-ynqeqjnshbs@public.gmane.org \
    --cc=attila-HB9FjVmMKa7tRgLqZ5aouw@public.gmane.org \
    --cc=broonie-GFdadSzt00ze9xe1eoZjHA@public.gmane.org \
    --cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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).