From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/4] Renesas sh-sci updates for v3.11
Date: Thu, 27 Jun 2013 13:57:24 +0000 [thread overview]
Message-ID: <20130627135724.GE28902@verge.net.au> (raw)
In-Reply-To: <201306271501.18968.arnd@arndb.de>
On Thu, Jun 27, 2013 at 03:01:18PM +0200, Arnd Bergmann wrote:
> On Wednesday 26 June 2013, Simon Horman wrote:
> > This revised pull-request includes a build-warning fix by myself.
> > The build-warning was reported by Arnd and has been acked by Greg
> > Kroah-Hartman.
> >
> > I apologise that this is now coming very late in the cycle, this is
> > mostly due to the time it took to address the build-warning.
>
> Ok. I've also had a simple merge conflict here, better make sure
> it's ok now.
Thanks. Your resolution appears to be the same as mine.
> Pulled into next/late.
>
> > I also apologise that I have not yet addressed your request to
> > drop your addresses from the CC list of the patch emails
> > that follow this one. I will do so before I start sending patches
> > for v3.12.
>
> No worries.
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2013-06-27 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 8:53 [PATCH v4 0/4] Renesas sh-sci updates for v3.11 Simon Horman
2013-06-26 8:53 ` [PATCH 1/4] serial: sh-sci: HSCIF support Simon Horman
2013-06-26 8:53 ` [PATCH 2/4] ARM: shmobile: r8a7790: " Simon Horman
2013-06-26 8:53 ` [PATCH 3/4] ARM: shmobile: r8a7790: don't use external clock for SCIFs Simon Horman
2013-06-26 12:33 ` Sergei Shtylyov
2013-06-26 8:53 ` [PATCH 4/4] serial: sh-sci: Initialise variables before access in sci_set_termios() Simon Horman
2013-06-27 13:01 ` [PATCH v4 0/4] Renesas sh-sci updates for v3.11 Arnd Bergmann
2013-06-27 13:57 ` 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=20130627135724.GE28902@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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