From: Arnd Bergmann <arnd@arndb.de>
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:01:18 +0000 [thread overview]
Message-ID: <201306271501.18968.arnd@arndb.de> (raw)
In-Reply-To: <1372236787-23342-1-git-send-email-horms+renesas@verge.net.au>
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.
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
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] Renesas sh-sci updates for v3.11
Date: Thu, 27 Jun 2013 15:01:18 +0200 [thread overview]
Message-ID: <201306271501.18968.arnd@arndb.de> (raw)
In-Reply-To: <1372236787-23342-1-git-send-email-horms+renesas@verge.net.au>
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.
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
next prev parent reply other threads:[~2013-06-27 13:01 UTC|newest]
Thread overview: 16+ 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 ` Simon Horman
2013-06-26 8:53 ` [PATCH 1/4] serial: sh-sci: HSCIF support Simon Horman
2013-06-26 8:53 ` Simon Horman
2013-06-26 8:53 ` [PATCH 2/4] ARM: shmobile: r8a7790: " Simon Horman
2013-06-26 8:53 ` 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 8:53 ` Simon Horman
2013-06-26 12:33 ` Sergei Shtylyov
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-26 8:53 ` Simon Horman
2013-06-27 13:01 ` Arnd Bergmann [this message]
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
2013-06-27 13:57 ` Simon Horman
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=201306271501.18968.arnd@arndb.de \
--to=arnd@arndb.de \
--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 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.