mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: monstr@seznam.cz
Cc: benh@kernel.crashing.org, Arnd Bergmann <arnd@arndb.de>,
	Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>,
	John Williams <john.williams@petalogix.com>,
	jwboyer@linux.vnet.ibm.com, John Linn <John.Linn@xilinx.com>,
	git-dev@xilinx.com, Grant Likely <grant.likely@secretlab.ca>,
	git@xilinx.com, microblaze-uclinux@itee.uq.edu.au,
	linux-kernel@vger.kernel.org
Subject: Re: Microblaze Linux release
Date: Wed, 16 Apr 2008 17:31:08 +1000	[thread overview]
Message-ID: <18437.43836.175638.137415@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <48059B92.7080601@seznam.cz>

Michal Simek writes:

> I think so. Sharing code among archs looks nice and this way is definitely
> right. But starting with communication with PowerPC guys that this code I want
> to use in case that this code is not in vanilla. This is not good start for
> doing this.

I have a commit queued up that moves lmb.c into the top-level lib
directory so other architectures can use it easily.  Dave Miller
wanted this so he could use it for sparc64.  That will go into Linus'
tree when the merge window opens and will be in 2.6.26.  So I don't
see any reason why microblaze couldn't use the LMB stuff.

Paul.

  reply	other threads:[~2008-04-16  7:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13 13:26 Michal Simek
2008-04-13 13:33 ` Grant Likely
2008-04-13 15:44   ` Michal Simek
2008-04-13 15:13 ` Josh Boyer
2008-04-13 18:50   ` Michal Simek
2008-04-14 15:55     ` Stephen Neuendorffer
2008-04-15 12:59       ` Michal Simek
2008-04-14  3:38 ` Arnd Bergmann
2008-04-14  5:10   ` H. Peter Anvin
2008-04-14  6:55     ` Arnd Bergmann
2008-04-14  6:01   ` Arnd Bergmann
2008-04-15 12:54     ` Michal Simek
2008-04-15 13:32       ` Arnd Bergmann
2008-04-15 21:52         ` Benjamin Herrenschmidt
2008-04-16  6:24           ` Michal Simek
2008-04-16  7:31             ` Paul Mackerras [this message]
2008-04-16  7:44               ` Arnd Bergmann
2008-04-16 15:28                 ` Michal Simek
2008-04-16 15:33                   ` Arnd Bergmann
2008-04-23 20:55                     ` Michal Simek
2008-04-23 20:57                       ` Florian Fainelli
2008-04-23 21:01                         ` Arnd Bergmann
2008-04-23 21:08                           ` Michal Simek
2008-04-23 21:22                         ` Michal Simek
2008-04-23 22:51                           ` John Williams
2008-04-16 15:26               ` Michal Simek
2008-04-16  7:45             ` Benjamin Herrenschmidt
2008-04-23 21:35           ` Michal Simek
2008-04-23 20:57         ` Michal Simek
2008-04-18 17:56       ` [microblaze-uclinux] " Stephen Neuendorffer
2008-04-19 10:38         ` Michal Simek
2008-04-14  7:10   ` Michal Simek

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=18437.43836.175638.137415@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=John.Linn@xilinx.com \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=git-dev@xilinx.com \
    --cc=git@xilinx.com \
    --cc=grant.likely@secretlab.ca \
    --cc=john.williams@petalogix.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=microblaze-uclinux@itee.uq.edu.au \
    --cc=monstr@seznam.cz \
    --cc=stephen.neuendorffer@xilinx.com \
    /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®