linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luke Yang <luke.adi@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: ADI Blackfin porting for kernel-2.6.13
Date: Fri, 23 Sep 2005 13:37:03 +0800	[thread overview]
Message-ID: <489ecd0c050922223736cf1548@mail.gmail.com> (raw)
In-Reply-To: <20050920071514.GA10909@plexity.net>

Hi all,

   This is the ADI Blackfin patch for kernel 2.6.13.  I know this
patch doesn' meet the kernel patch submission format, but this patch
is only for reviewing, shows the changes we made.  And I'll send new
patch for kernel 2.6.14 for you to merge into kernel.

   This patch mainly includes the arch/bfinnommu architecture files
and some blackfin specific drivers.  The only change to the common
files is that we change binfmt.c and related header file, added one
flat binary format for blackfin. We are considering removing this
change in next release.

  The patch is too big to put here , url is
http://blackfin.uclinux.org/frs/download.php/570/bfinnonnu-linux-2.6.13.patch

  Thanks!
Luke

On 9/20/05, Deepak Saxena <dsaxena@plexity.net> wrote:
> On Sep 20 2005, at 14:33, Luke Yang was caught saying:
> > Hi,
> >
> >    I am Luke Yang, an engineer from Analog Devices Inc. We ported
> > uclinux to our Blackfin cpu. Now we updated our architecture code for
> > kernel-2.6.13. I will send out a patch to this list.
> >
> >    I know kernel-2.6.14 is coming. Will the linux kernel accept our
> > patch for 2.6.13?
>
> Nope. 2.6.13 is now closed to new features as is 2.6.14 (unless it is
> a really sper special case that Linus feels is important enough to slip
> in).  At this point the best thing to do is to post your patches for review,
> make the changes that are asked, and be ready to post a patch vs 2.6.14
> within the first week after it is released so that it might be be picked
> up for 2.6.15.
>
> ~Deepak
>
> --
> Deepak Saxena - dsaxena@plexity.net - http://www.plexity.net
>
> Even a stopped clock gives the right time twice a day.
>

  reply	other threads:[~2005-09-23  5:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-20  6:33 ADI Blackfin porting for kernel-2.6.13 Luke Yang
2005-09-20  7:15 ` Deepak Saxena
2005-09-23  5:37   ` Luke Yang [this message]
2005-09-24 14:51     ` Robert Schwebel
2005-09-27  1:37       ` Luke Yang
2005-09-27  5:05         ` Robert Schwebel
2005-09-24 19:41     ` Jesper Juhl
2005-09-25  3:09     ` Jesper Juhl
2005-10-22 15:08 Jacques Moreau
2005-11-01 15:48 Robin Getz

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=489ecd0c050922223736cf1548@mail.gmail.com \
    --to=luke.adi@gmail.com \
    --cc=linux-kernel@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).