From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mediatek: soc updates for v4.2
Date: Mon, 01 Jun 2015 17:03:18 +0200 [thread overview]
Message-ID: <2065890.i1QSckCvO8@wuerfel> (raw)
In-Reply-To: <CABuKBe+2H8wFgaM+S-LAMm2B7DCXZKGetOOb9rkgTO4TjD7X=A@mail.gmail.com>
On Friday 29 May 2015 18:20:36 Matthias Brugger wrote:
> Hi Arnd,
>
> 2015-05-29 14:56 GMT+02:00 Arnd Bergmann <arnd@arndb.de>:
> > On Wednesday 27 May 2015 17:09:43 Matthias Brugger wrote:
> >> - pmic wrapper: fix clock handling
> >> - pmic wrapper: fix state machine
> >> - pmic wrapper: fix compile dependency
> >>
> >
> > Merged into next/drivers now.
> >
> > It looks like these are all bug fixes, and I wonder if they
> > should be merged for 4.1 and possibly backports instead.
> > Can you clarify?
>
> Yes, they should be merged for 4.1.
> I forgot about that.
> Sorry.
Ok, pulled into fixes now.
Arnd
prev parent reply other threads:[~2015-06-01 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 15:09 [GIT PULL] ARM: mediatek: soc updates for v4.2 Matthias Brugger
2015-05-29 12:56 ` Arnd Bergmann
2015-05-29 16:20 ` Matthias Brugger
2015-06-01 15:03 ` Arnd Bergmann [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=2065890.i1QSckCvO8@wuerfel \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox