From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: ixp4xx: fixes for v3.7
Date: Mon, 26 Nov 2012 13:14:32 +0000 [thread overview]
Message-ID: <201211261314.32662.arnd@arndb.de> (raw)
In-Reply-To: <0Lufa8-1TAtF11yb2-00zw9g@mx.kundenserver.de>
On Thursday 22 November 2012, Jason Cooper wrote:
> The following changes since commit f4a75d2eb7b1e2206094b901be09adb31ba63681:
>
> Linux 3.7-rc6 (2012-11-16 17:42:40 -0800)
>
> are available in the git repository at:
>
> git://git.infradead.org/users/jcooper/linux.git tags/ixp4xx_fixes_for_3.7
>
> for you to fetch changes up to 0d2c9f0517e915ce03a04e91d3207827e0d274a8:
>
> IXP4xx: use __iomem for MMIO (2012-11-22 03:36:45 +0000)
>
> ----------------------------------------------------------------
> ixp4xx fixes for v3.7
>
I've merged them into the fixes branch now, thanks a lot for following
up on these patches!
Olof, I'm undecided whether they are still appropriate for 3.7 since
we're past the final -rc now. If we want them in, we should probably
send them to Linus now and let him decide. For all I can tell, ixp4xx
is already completely broken without these patches, so there should be
no harm in including them, but then again " 13 files changed, 59
insertions(+), 68 deletions(-)" is slightly more than I'd like to send
at this point.
If you prefer, we can put them into next/fixes-non-critical, but then we
might want to mark more of them as candidates for stable.
Arnd
next parent reply other threads:[~2012-11-26 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0Lufa8-1TAtF11yb2-00zw9g@mx.kundenserver.de>
2012-11-26 13:14 ` Arnd Bergmann [this message]
2012-11-26 17:31 ` [GIT PULL] ARM: ixp4xx: fixes for v3.7 Olof Johansson
2012-11-26 18:54 ` Arnd Bergmann
2012-11-26 19:15 ` Olof Johansson
2012-11-22 4:21 Jason Cooper
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=201211261314.32662.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.