public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
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: Thu, 24 Jul 2008 09:28:32 +0100	[thread overview]
Message-ID: <1216888112.27026.28.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20080723151045.bcae107e.akpm@linux-foundation.org>

On Wed, 2008-07-23 at 15:10 -0700, Andrew Morton wrote:
> On Wed, 23 Jul 2008 22:10:22 +0100
> Catalin Marinas <catalin.marinas@arm•com> wrote:
> > To minimise the conflicts, what commit or tag id do you base your
> > current development branch on?
> 
> err, it's not that simple.  I just maintain plain old patches against
> linux-next.
> 
> Most git trees are based on current Linus mainline.

OK, it makes sense. I rebased the for-akpm branch onto Linus' latest git
tree.

-- 
Catalin

  reply	other threads:[~2008-07-24  8:28 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
2008-07-23 22:10             ` Andrew Morton
2008-07-24  8:28               ` Catalin Marinas [this message]
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=1216888112.27026.28.camel@pc1117.cambridge.arm.com \
    --to=catalin.marinas@arm$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)arm.linux.org.uk \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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