linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luke Yang <luke.adi@gmail.com>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ADI Blackfin porting for kernel-2.6.13
Date: Tue, 27 Sep 2005 09:37:59 +0800	[thread overview]
Message-ID: <489ecd0c05092618372a5993c5@mail.gmail.com> (raw)
In-Reply-To: <20050924145102.GD28883@pengutronix.de>

 We really don't have plan about Blackfin with a MMU now.  So do you
beleve it is necessary to change the name to arch/blackfin?

On 9/24/05, Robert Schwebel <r.schwebel@pengutronix.de> wrote:
> On Fri, Sep 23, 2005 at 01:37:03PM +0800, Luke Yang wrote:
> > This patch mainly includes the arch/bfinnommu architecture files and
> > some blackfin specific drivers.
>
> Having in mind the pain with arm and m68k with and without MMU, could
> you structure that thing in a way that it will be able to share the
> current nommu code with (hopefully coming) code for blackfins which
> might have a MMU? So it would be something like arch/blackfin.
>
> Robert
> --
>  Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
>  Pengutronix - Linux Solutions for Science and Industry
>    Handelsregister:  Amtsgericht Hildesheim, HRA 2686
>      Hannoversche Str. 2, 31134 Hildesheim, Germany
>    Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9
>
>

  reply	other threads:[~2005-09-27  1:38 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
2005-09-24 14:51     ` Robert Schwebel
2005-09-27  1:37       ` Luke Yang [this message]
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=489ecd0c05092618372a5993c5@mail.gmail.com \
    --to=luke.adi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=r.schwebel@pengutronix.de \
    /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).