From: Simon Horman <horms@verge.net.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arm-soc <arm@kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [GIT PULL v2 0/3] Renesas ARM64 Based SoC Defconfig Updates for v4.21
Date: Fri, 21 Dec 2018 08:42:29 +0900 [thread overview]
Message-ID: <20181220234225.iaodzrfok4d2ifl4@verge.net.au> (raw)
In-Reply-To: <CAK8P3a36OO+qM6r0BnrjWEWU6SV4SXu63Y=3Pq0FNt=56mzJXg@mail.gmail.com>
On Thu, Dec 20, 2018 at 05:38:45PM +0100, Arnd Bergmann wrote:
> > > ----------------------------------------------------------------
> > > Renesas ARM64 Based SoC Defconfig Updates for v4.21 (v2)
> > >
> > > * Enable in arm64 defconfig:
> > > - Renesas R-Car Gen3 PCIe PHY driver
> > > - Renesas R-Car thermal driver
> > > - ASoC simple SCU sound card support
> >
> > It seems that Morimoto-san has determined that the sound card patch is not
> > necessary. Rather than move to v3 for these not entirely critical changes I
> > would prefer to withdraw this pull request and revisit these changes for
> > v4.22 although if you do happen to pull this then I don't think any harm
> > would be done.
> >
> > I apologise for any inconvenience this may cause.
>
> No worries, I just dropped the pull request from my todo list for 4.21 now.
Great, thanks Arnd.
prev parent reply other threads:[~2018-12-20 23:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 11:56 [GIT PULL v2 0/3] Renesas ARM64 Based SoC Defconfig Updates for v4.21 Simon Horman
2018-12-18 9:44 ` Simon Horman
2018-12-20 16:38 ` Arnd Bergmann
2018-12-20 23:42 ` 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=20181220234225.iaodzrfok4d2ifl4@verge.net.au \
--to=horms@verge.net.au \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
/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).