From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Salter <msalter@redhat.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v3 00/24] C6X: New architecture
Date: Wed, 28 Sep 2011 16:33:05 +0200 [thread overview]
Message-ID: <201109281633.05583.arnd@arndb.de> (raw)
In-Reply-To: <20110928091542.9b1e35afa2075106550de7be@canb.auug.org.au>
On Wednesday 28 September 2011, Stephen Rothwell wrote:
> Show Details
> On Tue, 27 Sep 2011 16:29:41 -0400 Mark Salter <msalter@redhat.com> wrote:
> >
> > Here is v3 of the C6X architecture patch series. Patches are
> > available in 'upstream-v3' branch at:
> >
> > git@linux-c6x.org:/git/projects/linux-c6x-upstreaming
>
> Is it time for this to be included in linux-next (i.e. are you intending
> to send this to Linus during the next merge window)? If so, please send
> a request (cc'd to here, linux-next and linux-kernel) asking for
> inclusion. I would prefer a publically fetchable tree (the tree above is
> (implicitly) fetched over ssh and is so not generally available) and
> branch name that does not change over time (like "for-next" or something)
> but it can just be an alias for the above.
>
> Arnd, do you have an opinion on this?
From my perspective it can go into -next now. All the issues I have
reported in version 2 have been fixed, and the comments I made this
time are relatively insignificant, so I trust that Mark can fix those
either between now and the merge window or provide updates during the
3.2 bug fix phase. The only thing that absolutely needs to get fixed
before 3.2.0 IMO is the ptrace ABI since we can no longer change that
after a release, but it should also be a trivial change.
Thomas, you also had some important comments, please complain if you
see those as show-stoppers for integration into linux-next.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Salter <msalter@redhat.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v3 00/24] C6X: New architecture
Date: Wed, 28 Sep 2011 16:33:05 +0200 [thread overview]
Message-ID: <201109281633.05583.arnd@arndb.de> (raw)
In-Reply-To: <20110928091542.9b1e35afa2075106550de7be@canb.auug.org.au>
On Wednesday 28 September 2011, Stephen Rothwell wrote:
> Show Details
> On Tue, 27 Sep 2011 16:29:41 -0400 Mark Salter <msalter@redhat.com> wrote:
> >
> > Here is v3 of the C6X architecture patch series. Patches are
> > available in 'upstream-v3' branch at:
> >
> > git@linux-c6x.org:/git/projects/linux-c6x-upstreaming
>
> Is it time for this to be included in linux-next (i.e. are you intending
> to send this to Linus during the next merge window)? If so, please send
> a request (cc'd to here, linux-next and linux-kernel) asking for
> inclusion. I would prefer a publically fetchable tree (the tree above is
> (implicitly) fetched over ssh and is so not generally available) and
> branch name that does not change over time (like "for-next" or something)
> but it can just be an alias for the above.
>
> Arnd, do you have an opinion on this?
>From my perspective it can go into -next now. All the issues I have
reported in version 2 have been fixed, and the comments I made this
time are relatively insignificant, so I trust that Mark can fix those
either between now and the merge window or provide updates during the
3.2 bug fix phase. The only thing that absolutely needs to get fixed
before 3.2.0 IMO is the ptrace ABI since we can no longer change that
after a release, but it should also be a trivial change.
Thomas, you also had some important comments, please complain if you
see those as show-stoppers for integration into linux-next.
Arnd
next prev parent reply other threads:[~2011-09-28 14:33 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 20:29 [PATCH v3 00/24] C6X: New architecture Mark Salter
2011-09-27 20:29 ` [PATCH v3 01/24] fix default __strnlen_user macro Mark Salter
2011-09-28 13:20 ` Arnd Bergmann
2011-09-27 20:29 ` [PATCH v3 02/24] fixed generic page.h for non-zero PAGE_OFFSET Mark Salter
2011-09-27 20:29 ` [PATCH v3 03/24] add ELF machine define for TI C6X DSPs Mark Salter
2011-09-27 20:29 ` [PATCH v3 04/24] add missing __iomem to generic iounmap declaration Mark Salter
2011-09-28 13:19 ` Arnd Bergmann
2011-09-27 20:29 ` [PATCH v3 05/24] C6X: build infrastructure Mark Salter
2011-09-28 13:23 ` Arnd Bergmann
2011-09-28 14:32 ` Mark Salter
2011-09-28 14:57 ` Arnd Bergmann
2011-09-27 20:29 ` [PATCH v3 06/24] C6X: early boot code Mark Salter
2011-09-28 13:26 ` Arnd Bergmann
2011-09-28 14:06 ` Mark Salter
2011-09-28 15:00 ` Arnd Bergmann
2011-09-27 20:29 ` [PATCH v3 07/24] C6X: devicetree support Mark Salter
2011-09-28 13:31 ` Arnd Bergmann
2011-09-28 14:44 ` Mark Salter
2011-09-28 14:57 ` Arnd Bergmann
2011-09-28 23:11 ` Grant Likely
2011-09-27 20:29 ` [PATCH v3 08/24] C6X: memory management and DMA support Mark Salter
2011-09-28 13:46 ` Arnd Bergmann
2011-09-27 20:29 ` [PATCH v3 09/24] C6X: process management Mark Salter
2011-09-28 13:47 ` Arnd Bergmann
2011-09-27 20:29 ` [PATCH v3 10/24] C6X: signal management Mark Salter
2011-09-28 13:48 ` Arnd Bergmann
2011-09-27 20:29 ` [PATCH v3 11/24] C6X: time management Mark Salter
2011-09-27 23:41 ` Thomas Gleixner
2011-09-28 12:48 ` Mark Salter
2011-09-27 20:29 ` [PATCH v3 12/24] C6X: interrupt handling Mark Salter
2011-09-27 23:30 ` Thomas Gleixner
2011-09-27 20:29 ` [PATCH v3 13/24] C6X: syscalls Mark Salter
2011-09-28 13:49 ` Arnd Bergmann
2011-09-27 20:29 ` [PATCH v3 14/24] C6X: traps Mark Salter
2011-09-28 13:50 ` Arnd Bergmann
2011-09-27 20:29 ` [PATCH v3 15/24] C6X: clocks Mark Salter
2011-09-28 13:51 ` Arnd Bergmann
2011-09-27 20:29 ` [PATCH v3 16/24] C6X: cache control Mark Salter
2011-09-28 13:52 ` Arnd Bergmann
2011-09-27 20:29 ` [PATCH v3 17/24] C6X: loadable module support Mark Salter
2011-09-28 13:54 ` Arnd Bergmann
2011-09-27 20:29 ` [PATCH v3 18/24] C6X: ptrace support Mark Salter
2011-09-28 13:57 ` Arnd Bergmann
2011-09-27 20:30 ` [PATCH v3 19/24] C6X: headers Mark Salter
2011-09-28 14:07 ` Arnd Bergmann
2011-09-29 13:32 ` Mark Salter
2011-09-29 14:24 ` Mark Salter
2011-09-29 14:41 ` Arnd Bergmann
2011-09-27 20:30 ` [PATCH v3 20/24] C6X: library code Mark Salter
2011-09-28 14:09 ` Arnd Bergmann
2011-09-27 20:30 ` [PATCH v3 21/24] C6X: general SoC support Mark Salter
2011-09-28 14:19 ` Arnd Bergmann
2011-09-27 20:30 ` [PATCH v3 22/24] C6X: EMIF - External Memory Interface Mark Salter
2011-09-28 14:13 ` Arnd Bergmann
2011-09-27 20:30 ` [PATCH v3 23/24] C6X: DSCR - Device State Configuration Registers Mark Salter
2011-09-28 14:11 ` Arnd Bergmann
2011-09-27 20:30 ` [PATCH v3 24/24] C6X: MAINTAINERS Mark Salter
2011-09-28 14:09 ` Arnd Bergmann
2011-09-27 23:15 ` [PATCH v3 00/24] C6X: New architecture Stephen Rothwell
2011-09-28 14:33 ` Arnd Bergmann [this message]
2011-09-28 14:33 ` Arnd Bergmann
2011-09-28 21:49 ` Valdis.Kletnieks
2011-09-29 10:33 ` Arnd Bergmann
2011-09-29 12:21 ` Mark Salter
2011-09-29 12:42 ` Valdis.Kletnieks
2011-09-29 13:02 ` Mark Salter
2011-09-29 13:18 ` 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=201109281633.05583.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msalter@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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.