From: Michal Simek <monstr@seznam.cz>
To: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>,
John Williams <john.williams@petalogix.com>,
jwboyer@linux.vnet.ibm.com, benh@kernel.crashing.org,
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, paulus@samba.org
Subject: Microblaze Linux release
Date: Sun, 13 Apr 2008 15:26:57 +0200 [thread overview]
Message-ID: <48020A21.4000404@seznam.cz> (raw)
Hi Everybody,
I fixed all reported bugs which I got from LKML and from you.
Latest version of Microblaze Linux kernel is available at git.monstr.eu.
There is git repository called linux-microblaze.git
Microblaze port is based on 2.6.24-rc5. I'll create the new repo with clean pack
of changes based on latest kernel version for easier pull.
Merge windows will be open hopefully next week and I would like to send pull
request to Paul.
I would like to ask you for review all microblaze code especially
arch/microblaze and include/asm-microblaze. Please don't send me question to
drivers - Microblaze will use only uartlite driver (only add on or to Kconfig -
that's enough for now).
All questions and reported bug please send to me.
Please report all bugs (coding style, long line, poor coments - everything).
Please send me your ACK too. For my better summary - please send me list of
files. Summary will be continuously concurrently publish at
http://www.monstr.eu/wiki/doku.php?id=kernel:kernel.
Thanks for your help,
Michal Simek,
www.monstr.eu
P.S.: For LKML users - I am going to integrate all bugs to previous set of
patches - that's why I asked about how to do it. I hope I send this pack today
or on Monday.
next reply other threads:[~2008-04-13 13:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 13:26 Michal Simek [this message]
2008-04-13 13:33 ` Microblaze Linux release 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
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=48020A21.4000404@seznam.cz \
--to=monstr@seznam.cz \
--cc=John.Linn@xilinx.com \
--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=paulus@samba.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.