From: Catalin Marinas <catalin.marinas@arm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-next@vger.kernel.org
Subject: Re: [PATCH 00/12] Thumb-2 kernel support
Date: Wed, 23 Jul 2008 22:10:22 +0100 [thread overview]
Message-ID: <1216847422.6550.8.camel@localhost.localdomain> (raw)
In-Reply-To: <20080723130140.ff016944.akpm@linux-foundation.org>
On Wed, 2008-07-23 at 13:01 -0700, Andrew Morton wrote:
> On Wed, 23 Jul 2008 17:05:55 +0100
> Catalin Marinas <catalin.marinas@arm.com> wrote:
> > Were the Thumb-2 patches merged in any of the -mm tree releases? I now
> > updated the series to the 2.6.26-rc8-mm1 kernel if you still consider
> > merging them (___git://linux-arm.org/linux-2.6 for-akpm).
>
> I pull it regularly but always get rejects and never got around to
> looking into fixing them. Probably the git-thumb tree is based on an
> ARM git tree so I'd need to generate the diff reletive to that tree.
> But I just haven't got onto it, sorry.
I only based the for-akpm branch on your latest -mm tree release but
since you are rebasing your tree with every release, the base of my tree
(currently 2.6.26-rc8-mm1) is probably not an ancestor of your
development branch, hence the merging errors.
To minimise the conflicts, what commit or tag id do you base your
current development branch on?
> > Russell (and others in the ARM community), are you OK with this set of
> > patches being merged into 2.6.28 mainline (i.e. at the next merging
> > window)? If yes, do you acknowledge the patches? In the meantime, I can
> > rebase them on top of linux-next to check for possible merge conflicts
> > (or even ask for them to be pulled into linux-next).
>
> yup, we should maintain the tree in linux-next if it's for 2.6.28.
I'm waiting for Russell to ack the patches first.
Thanks.
--
Catalin
next prev parent reply other threads:[~2008-07-23 21:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080606173300.7930.31525.stgit@pc1117.cambridge.arm.com>
2008-06-30 19:51 ` [PATCH 00/12] Thumb-2 kernel support Andrew Morton
2008-07-01 8:32 ` Catalin Marinas
2008-07-01 8:45 ` Andrew Morton
2008-07-23 16:05 ` Catalin Marinas
2008-07-23 20:01 ` Andrew Morton
2008-07-23 21:10 ` Catalin Marinas [this message]
2008-07-23 22:10 ` Andrew Morton
2008-07-24 8:28 ` Catalin Marinas
2008-07-27 11:08 ` Russell King - ARM Linux
2008-07-28 11:45 ` Catalin Marinas
2008-07-28 12:40 ` Catalin Marinas
2008-07-28 12:53 ` Russell King - ARM Linux
2008-08-12 2:07 ` Nicolas Pitre
2008-07-28 12:50 ` Russell King - ARM Linux
2008-07-28 14:41 ` Catalin Marinas
2008-08-12 2:17 ` Nicolas Pitre
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=1216847422.6550.8.camel@localhost.localdomain \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-next@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).