From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Matthias Brugger <matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Louis Yu <louis.yu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
HenryC Chen <henryc.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
"moderated list:ARM/Mediatek SoC..."
<linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
John Crispin <blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
Subject: Re: [GIT PULL] ARM: mediatek: soc updates for v4.5
Date: Fri, 26 Feb 2016 22:27:58 +0100 [thread overview]
Message-ID: <4249031.5hymV8HWSB@wuerfel> (raw)
In-Reply-To: <CABuKBeKf4dB7Y6A9WN530Zfmk55TXYserHv9OL-8Atfg65tTjA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Monday 22 February 2016 13:44:00 Matthias Brugger wrote:
> Hi,
>
> These updates are of course for v4.6, sorry for the confusion.
>
And I mixed up the branch, it's in next/soc of course, not next/dt ;-)
Arnd
next prev parent reply other threads:[~2016-02-26 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 12:40 [GIT PULL] ARM: mediatek: soc updates for v4.5 Matthias Brugger
[not found] ` <CABuKBeLEf+jyE5gzWEVzfRZ7DwRgnLrdWLREwqqfYGBb2g+exQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-22 12:44 ` Matthias Brugger
[not found] ` <CABuKBeKf4dB7Y6A9WN530Zfmk55TXYserHv9OL-8Atfg65tTjA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-26 21:27 ` Arnd Bergmann [this message]
2016-02-26 21:24 ` 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=4249031.5hymV8HWSB@wuerfel \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org \
--cc=henryc.chen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=louis.yu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@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