From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/1] ARM: shmobile: Remove duplicate inclusion of dma-mapping.h in setup-r8a7740.c
Date: Mon, 03 Dec 2012 07:29:39 +0000 [thread overview]
Message-ID: <20121203072937.GA1214@verge.net.au> (raw)
In-Reply-To: <1353393549-1532-1-git-send-email-sachin.kamat@linaro.org>
On Mon, Dec 03, 2012 at 09:43:14AM +0530, Sachin Kamat wrote:
> On 30 November 2012 14:26, Simon Horman <horms@verge.net.au> wrote:
> > On Tue, Nov 27, 2012 at 09:05:25AM +0530, Sachin Kamat wrote:
> >> ping
> >
> > Sorry for missing this. I have applied it now and
>
> Thanks Simon.
>
> > I expect it will be included in 3.9.
>
> Oh. I thought it might get included in 3.8 itself.
Sorry, due to the path that patches for shmobile take to the kernel
its already a bit too late for 3.8.
prev parent reply other threads:[~2012-12-03 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 6:51 [PATCH 1/1] ARM: shmobile: Remove duplicate inclusion of dma-mapping.h in setup-r8a7740.c Sachin Kamat
2012-11-27 3:47 ` Sachin Kamat
2012-11-30 8:56 ` Simon Horman
2012-12-03 4:25 ` Sachin Kamat
2012-12-03 7:29 ` Simon Horman [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=20121203072937.GA1214@verge.net.au \
--to=horms@verge.net.au \
--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 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).