LKML Archive on
help / color / mirror / Atom feed
From: "Wu, Bryan" <>
To: Andrew Morton <>
Cc:, Arnd Bergmann <>,
	Paul Mundt <>,
	bert hubert <>,
Subject: Re: [PATCH -mm 1/4] Blackfin: architecture update patch
Date: Thu, 22 Mar 2007 13:47:53 +0800	[thread overview]
Message-ID: <1174542473.20061.23.camel@roc-desktop> (raw)
In-Reply-To: <>

On Wed, 2007-03-21 at 20:08 -0800, Andrew Morton wrote:
> On Thu, 22 Mar 2007 10:24:51 +0800 "Wu, Bryan" <> wrote:
> > > 1 out of 1 hunk FAILED -- saving rejects to file include/asm-blackfin/cplbinit.h.rej
> > > 1 out of 1 hunk FAILED -- saving rejects to file include/asm-blackfin/mach-bf535/bf535.h.rej
> > > 1 out of 1 hunk FAILED -- saving rejects to file include/asm-blackfin/scatterlist.h.rej
> > > 
> > > This seems to be against a kernel which did not include
> > > blackfin-arch-balance-parenthesis-in-macros.patch.  But 2.6.21-rc4-mm1 did
> > > include blackfin-arch-balance-parenthesis-in-macros.patch, so I'm not sure
> > > what is going on here.
> > > 
> > 
> > Sorry for this mess up. you know, as
> > blackfin-arch-balance-parenthesis-in-macros.patch was posted, it was
> > applied to our SVN tree. And I just merged these weeks SVN change to
> > this update patch. So this patch includes
> > blackfin-arch-balance-parenthesis-in-macros.patch. 
> Well, you'd better get used to it.  As I told you a few weeks ago, once this
> code is merged into mainline you no longer own the master copy of the blackfin
> tree - Linus does.

We agree with this and please give us sometime to try to push our
patches to the mainline tree. We still have tons of code should be
submitted to mainline, and before the submission, the code should be
reviewed and fixed. This is my main task and I think this internal
review can reduce you and other kernel maintainer's effort.

But our team still have release pressure from customers. The whole
distribution including bootloader/toolchain/kernel/uClinux-dist should
be delivered to customers on time. If our kernel blackfin-arch are
merged eventually, we definitely will move to linus tree and ask our
customer to use linus mainline tree.

As you know, our latest U-Boot blackfin code is accepted by U-Boot
upstream mainline recently. Then the internal U-Boot SVN tree will be
replaced by upstream git-blackfin tree in U-Boot, our development will
move to that mainline tree.

At this moment, I will try my best to speed up the blackfin-arch and
drivers merge progress. 

> If you're not careful, you'll end up submitting patches which revert other
> people's fixes.   And there's an excellent chance that you will submit patches
> which have dependencies on other stuff in your private tree and which are
> insufficiently-tested-against, and possibly incorrect-against Linus's tree.

Apologise. I will resend the blackfin update patch based on other

Thanks Andrew
-Bryan Wu

  reply	other threads:[~2007-03-22  5:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1174472363.5648.58.camel@roc-desktop>
2007-03-21 22:53 ` Andrew Morton
2007-03-22  2:24   ` Wu, Bryan
2007-03-22  4:08     ` Andrew Morton
2007-03-22  5:47       ` Wu, Bryan [this message]
     [not found] <1174471618.5648.50.camel@roc-desktop>
2007-03-21 10:25 ` Arnd Bergmann
2007-03-21 10:33   ` Wu, Bryan
2007-03-21 10:38     ` Arnd Bergmann
2007-03-21 12:56 ` Paul Mundt
2007-03-21 15:39   ` Mike Frysinger
2007-03-21 13:06 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1174542473.20061.23.camel@roc-desktop \ \ \ \ \ \ \
    --subject='Re: [PATCH -mm 1/4] Blackfin: architecture update patch' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).