From: Paul Mundt <lethal@linux-sh.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
Chris Ball <cjb@laptop.org>
Subject: Re: [PATCH 0/2] mmc: sh_mmcif: simplify platform DMA configuration
Date: Mon, 5 Sep 2011 13:15:54 +0900 [thread overview]
Message-ID: <20110905041553.GB22142@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1108301819150.19151@axis700.grange>
On Tue, Aug 30, 2011 at 06:26:34PM +0200, Guennadi Liakhovetski wrote:
> A simple cosmetic clean-up, no functional changes. Patch 2/2 depends on
> patch 1/2 and can wait until 3.3. Paul, would you be able to put it under
> the carpet somewhere until then or shall I resend it after 3.2-rc1 is out?
> After both these patches have been applied, we can remove struct
> sh_mmcif_plat_data::dma around 3.4 or 4.0 or whatever;-)
>
It's not a problem, I'll just flag it as awaiting upstream in the
tracker. Anything flagged as such I generally give a once over after each
merge window to see if their dependencies have been worked out.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/2] mmc: sh_mmcif: simplify platform DMA configuration
Date: Mon, 05 Sep 2011 04:15:54 +0000 [thread overview]
Message-ID: <20110905041553.GB22142@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1108301819150.19151@axis700.grange>
On Tue, Aug 30, 2011 at 06:26:34PM +0200, Guennadi Liakhovetski wrote:
> A simple cosmetic clean-up, no functional changes. Patch 2/2 depends on
> patch 1/2 and can wait until 3.3. Paul, would you be able to put it under
> the carpet somewhere until then or shall I resend it after 3.2-rc1 is out?
> After both these patches have been applied, we can remove struct
> sh_mmcif_plat_data::dma around 3.4 or 4.0 or whatever;-)
>
It's not a problem, I'll just flag it as awaiting upstream in the
tracker. Anything flagged as such I generally give a once over after each
merge window to see if their dependencies have been worked out.
next prev parent reply other threads:[~2011-09-05 4:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 16:26 [PATCH 0/2] mmc: sh_mmcif: simplify platform DMA configuration Guennadi Liakhovetski
2011-08-30 16:26 ` Guennadi Liakhovetski
2011-08-30 16:26 ` [PATCH 1/2] mmc: sh_mmcif: simplify platform data Guennadi Liakhovetski
2011-08-30 16:26 ` Guennadi Liakhovetski
2011-09-21 18:43 ` Chris Ball
2011-09-21 18:43 ` Chris Ball
2011-08-30 16:26 ` [PATCH 2/2] ARM: mach-shmobile: simplify MMCIF DMA configuration Guennadi Liakhovetski
2011-08-30 16:26 ` Guennadi Liakhovetski
2011-09-05 4:15 ` Paul Mundt [this message]
2011-09-05 4:15 ` [PATCH 0/2] mmc: sh_mmcif: simplify platform " Paul Mundt
2011-09-05 7:15 ` Guennadi Liakhovetski
2011-09-05 7:15 ` Guennadi Liakhovetski
2012-01-17 16:39 ` Guennadi Liakhovetski
2012-01-17 16:39 ` Guennadi Liakhovetski
2012-01-18 0:21 ` Paul Mundt
2012-01-18 0:21 ` Paul Mundt
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=20110905041553.GB22142@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.