From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] [v3.3] fixes for arch-pxa in arm
Date: Tue, 21 Feb 2012 17:27:19 +0000 [thread overview]
Message-ID: <201202211727.19754.arnd@arndb.de> (raw)
In-Reply-To: <CAN1soZzwvefsZbJ4LXk-j0qjqQLTH-7Gp4ufgyncjbu-SevnZg@mail.gmail.com>
On Tuesday 21 February 2012, Haojian Zhuang wrote:
> On Sat, Feb 18, 2012 at 6:04 PM, Haojian Zhuang
> <haojian.zhuang@gmail.com> wrote:
> > Hi Arnd,
> >
> > Here's the fixes for 3.3.
> >
> > The following changes since commit c38e23456278e967f094b08247ffc3711b1029b2:
> >
> > i387: fix sense of sanity check (2012-02-15 08:05:18 -0800)
> >
> > are available in the git repository at:
> > git://github.com/hzhuang1/linux.git fixes
> >
> > Axel Lin (2):
> > ARM: pxa: fix error handling in pxa2xx_drv_pcmcia_probe
> > pxa/hx4700: add platform device and I2C info for AK4641 codec
> >
> > Danny Kukawka (3):
> > ARM: pxa: fix including linux/gpio.h twice
> > arch/arm/mach-mmp/: some files include some headers twice
> > arch/arm/mach-pxa/: included linux/gpio.h twice
> >
> > Haojian Zhuang (2):
> > ARM: pxa: fix wrong parsing gpio event on spitz
> > ARM: pxa: fix mixed declarations and code in sharpsl_pm
Hi Haojian,
I've had a look now, sorry for the late reply.
How urgent is "pxa/hx4700: add platform device and I2C info
for AK4641 codec" amongst these? If not so urgent, I would prefer
putting this one on next/fixes-non-critical or even next/board
for 3.4 while applying the reset on the fixes branch for 3.3.
I'd prefer to cut down on non-trivial fixes for 3.3 now that
we are at -rc4.
Arnd
next prev parent reply other threads:[~2012-02-21 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-18 10:04 [GIT PULL] [v3.3] fixes for arch-pxa in arm Haojian Zhuang
[not found] ` <CAN1soZzwvefsZbJ4LXk-j0qjqQLTH-7Gp4ufgyncjbu-SevnZg@mail.gmail.com>
2012-02-21 17:27 ` Arnd Bergmann [this message]
2012-02-21 23:59 ` Axel Lin
2012-02-22 13:12 ` 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=201202211727.19754.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.