From: Paul Mundt <lethal@linux-sh.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Mike Frysinger <vapier.adi@gmail.com>
Cc: Chris Zankel <chris@zankel.net>, Johannes Weiner <jw@emlix.com>,
linux-kernel@vger.kernel.org, Oskar Schirmer <os@emlix.com>,
Greg Ungerer <gerg@snapgear.com>
Subject: Re: Xtensa patches
Date: Thu, 16 Apr 2009 18:06:23 +0900 [thread overview]
Message-ID: <20090416090623.GA30877@linux-sh.org> (raw)
In-Reply-To: <20090416015601.d4114f73.akpm@linux-foundation.org>
On Thu, Apr 16, 2009 at 01:56:01AM -0700, Andrew Morton wrote:
> On Thu, 16 Apr 2009 17:30:00 +0900 Paul Mundt <lethal@linux-sh.org> wrote:
> > On Thu, Apr 16, 2009 at 01:24:47AM -0700, Andrew Morton wrote:
> > > OK. I have a random pile if i-dont-know-what xtensa stuff here.
> > >
> > > xtensa-add-flat-support-checkpatch-fixes.patch
> > > xtensa-variant-specific-code.patch
> > > xtensa-cache-inquiry-and-unaligned-cache-handling-functions.patch
> > > xtensa-s6000-dma-engine-support.patch
> > > xtensa-allow-platform-and-variant-to-initialize-own-irq-chips.patch
> > > xtensa-support-s6000-gpio-irqs-and-alternate-function-selection.patch
> > > s6gmac-xtensa-s6000-on-chip-ethernet-driver.patch
> > > s6gmac-xtensa-s6000-on-chip-ethernet-driver-fix.patch
> > > xtensa-s6105-specific-configuration-for-s6gmac.patch
> > > xtensa-enable-s6gmac-in-s6105_defconfig.patch
> > > xtensa-add-m41t62-rtc-to-s6105-platform.patch
> > > xtensa-enable-m41t80-driver-in-s6105_defconfig.patch
> > >
> > > I'll drop xtensa-add-flat-support-checkpatch-fixes.patch (as I usually
> > > do when someone merges the base patch but doesn't run checkpatch on it
> > > - hint) and I'll send the rest over at you.
> > >
> > Presumably the nommu xtensa bits still depend on
> >
> > flat-fix-data-sections-alignment.patch
> >
> > ?
>
> I don't think I ever knew that.
>
http://lkml.org/lkml/2009/4/9/241
> What's happening with flat-fix-data-sections-alignment.patch, btw? It
> seems to be stuck.
>
As far as I know it was just waiting on Mike to comment, as he was the
only other one with concerns. Mike?
next prev parent reply other threads:[~2009-04-16 9:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 9:41 Johannes Weiner
2009-04-14 9:41 ` [patch 01/12] xtensa: always use correct stack pointer for stack traces Johannes Weiner
2009-04-14 9:41 ` [patch 02/12] xtensa: register gpio chip before use Johannes Weiner
2009-04-14 9:41 ` [patch 03/12] xtensa: fix wrong extern declaration renamed in code using it Johannes Weiner
2009-04-14 9:41 ` [patch 04/12] xtensa: implement ccount calibration for s6000 Johannes Weiner
2009-04-14 9:41 ` [patch 05/12] xtensa: update s6105_defconfig for ccount calibration Johannes Weiner
2009-04-14 9:41 ` [patch 06/12] xtensa: implement CLK API Johannes Weiner
2009-04-14 9:41 ` [patch 07/12] xtensa: implement PTRACE_PEEKUSER addresses for nommu Johannes Weiner
2009-04-14 9:41 ` [patch 08/12] xtensa: s6000 dma engine support Johannes Weiner
2009-04-14 9:41 ` [patch 09/12] xtensa: allow platform and variant to initialize own irq chips Johannes Weiner
2009-04-23 7:19 ` Chris Zankel
2009-04-23 16:16 ` Daniel Glöckner
2009-04-14 9:41 ` [patch 10/12] xtensa: support s6000 gpio irqs and alternate function selection Johannes Weiner
2009-04-14 9:41 ` [patch 11/12] xtensa: s6105 specific configuration for s6gmac Johannes Weiner
2009-04-14 9:41 ` [patch 12/12] xtensa: enable s6gmac in s6105_defconfig Johannes Weiner
2009-04-16 7:42 ` Xtensa patches Chris Zankel
2009-04-16 8:24 ` Andrew Morton
2009-04-16 8:30 ` Paul Mundt
2009-04-16 8:56 ` Andrew Morton
2009-04-16 9:06 ` Paul Mundt [this message]
2009-04-16 8:35 ` Stephen Rothwell
2009-04-16 9:15 ` Chris Zankel
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=20090416090623.GA30877@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=chris@zankel.net \
--cc=gerg@snapgear.com \
--cc=jw@emlix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=os@emlix.com \
--cc=vapier.adi@gmail.com \
/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