mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luke Yang <luke.adi@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ADI Blackfin patch for kernel 2.6.14
Date: Fri, 4 Nov 2005 12:59:14 +0800	[thread overview]
Message-ID: <489ecd0c0511032059n394abbb2s9865c22de9b2c448@mail.gmail.com> (raw)
In-Reply-To: <489ecd0c0511012306w434d75fbs90e1969d82a07922@mail.gmail.com>

Hi,

  Does this patch has the chance to be merged? Is anyone reivewing or
merging it? Anything I can help? Just want to make sure... Thanks a
lot!

Luke Yang

On 11/2/05, Luke Yang <luke.adi@gmail.com> wrote:
> Hi,
>
>   Thank you for your reivew. I change those files and updated the patch:
>
> http://blackfin.uclinux.org/frs/download.php/607/bfin_r2_4kernel-2.6.14.patch
>
> Regards,
> Luke
>
>
> On 11/2/05, Adrian Bunk <bunk@stusta.de> wrote:
> > On Tue, Nov 01, 2005 at 05:28:30PM +0800, Luke Yang wrote:
> >
> > > Hi all,
> >
> > Hi,
> >
> > >   This is the new Blackfin patch for kernel 2.6.14. Mainly includes
> > > arch/Blackfin and include/asm-blackfin files. We decided not to put in
> > > all the drivers for this version.
> > >
> > >  Here is the patch URL:
> > >  http://blackfin.uclinux.org/frs/download.php/606/bfin4kernel-2.6.14.patch
> > > . Please reiview and merge it into the kernel. Thank you very much.
> >
> > some comments:
> > - the changes to the toplevel Makefile should go to
> >   arch/blackfin/kernel/Makefile
> > - please use drivers/Kconfig
> > - include/asm-blackfin/pci.h contains some ^M characters
> > - please replace "extern inline" and "extern __inline__" with
> >   "static inline"
> > - CONFIG_CLEAN_COMPILE=n is not a good choice for a defconfig
> >
> > > Luke Yang
> >
> > cu
> > Adrian
> >
> > --
> >
> >        "Is there not promise of rain?" Ling Tan asked suddenly out
> >         of the darkness. There had been need of rain for many days.
> >        "Only a promise," Lao Er said.
> >                                        Pearl S. Buck - Dragon Seed
> >
> >
>

  reply	other threads:[~2005-11-04  4:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01  9:28 Luke Yang
2005-11-01 16:51 ` Adrian Bunk
2005-11-02  7:06   ` Luke Yang
2005-11-04  4:59     ` Luke Yang [this message]
2005-11-04 23:06       ` Greg KH
2005-11-07  6:58         ` Luke Yang
2005-11-07 16:59           ` Greg KH
2005-11-08  7:50             ` Andrew Morton
2005-11-11 11:26               ` Luke Yang
2005-11-12 11:58                 ` Andrey Volkov
2005-11-14  7:22                   ` Luke Yang
2005-11-12 21:47                 ` Greg KH
2005-11-13 14:22                   ` Bernd Schmidt
2005-11-14  7:34                   ` Luke Yang
2005-11-14  7:52                     ` Arjan van de Ven
2005-11-15  2:40                       ` Luke Yang
2005-11-15  4:14                         ` Greg KH
2005-11-14 12:53                     ` Alan Cox
2005-11-16  3:44               ` Luke Yang
2005-11-16  6:11                 ` Paul Jackson
2005-11-16  6:34                   ` Luke Yang
2005-11-16 13:42               ` Bernd Schmidt
2005-11-14 20:53 Robin Getz
2005-11-15 19:11 ` Matthieu CASTET
2005-11-17  5:38 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=489ecd0c0511032059n394abbb2s9865c22de9b2c448@mail.gmail.com \
    --to=luke.adi@gmail.com \
    --cc=bunk@stusta.de \
    --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

all inboxes | Powered by JetHome®