From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: "Andrew-CT Chen"
<andrew-ct.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
"Bayi Cheng" <bayi.cheng-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
"moderated list:ARM/Mediatek SoC..."
<linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"Matthias Brugger"
<matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"Eddie Huang (黃智傑)"
<eddie.huang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
Subject: Re: [GIT PULL] ARM: mediatek: dts updates for v4.6
Date: Fri, 26 Feb 2016 22:31:30 +0100 [thread overview]
Message-ID: <2947440.eXCb0RRaIr@wuerfel> (raw)
In-Reply-To: <CABuKBeK+zT85Z695dBGO-0tU26w5LBJqS53aecdZYGZ6V0GPhA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Monday 22 February 2016 13:43:15 Matthias Brugger wrote:
>
> Please pull the following patches.
> As you can see from the description, this pull request includes some
> fixes. Only a few developer have access to a Mediatek HW at the
> moment. Therefore I didn't send the fixes to stable.
>
> If you want me to send the fixes for older kernel versions, please let me know.
I think it's fine either way here, up to you.
Pulled into next/dts64, thanks!
Arnd
next prev parent reply other threads:[~2016-02-26 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 12:43 [GIT PULL] ARM: mediatek: dts updates for v4.6 Matthias Brugger
[not found] ` <CABuKBeK+zT85Z695dBGO-0tU26w5LBJqS53aecdZYGZ6V0GPhA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-22 12:48 ` Matthias Brugger
2016-02-26 21:31 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 12:47 Matthias Brugger
[not found] ` <CABuKBe+vk0E6-8ni5bHtyn6X3EbLoOxfjw0zqPRE_tLdp0AAXQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-26 21:26 ` Arnd Bergmann
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=2947440.eXCb0RRaIr@wuerfel \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=andrew-ct.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=bayi.cheng-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=eddie.huang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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