From: Michal Simek <monstr@seznam.cz>
To: Linux Kernel list <linux-kernel@vger.kernel.org>,
torvalds@linux-foundation.org,
John Williams <john.williams@petalogix.com>,
Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>,
John Linn <John.Linn@xilinx.com>, Jon Loeliger <jdl@jdl.com>,
David Gibson <david@gibson.dropbear.id.au>,
Arnd Bergmann <arnd@arndb.de>, Sam Ravnborg <sam@ravnborg.org>
Subject: Microblaze architecture - ACK
Date: Mon, 14 Jul 2008 11:18:24 +0200 [thread overview]
Message-ID: <487B19E0.3030301@seznam.cz> (raw)
Hi All,
as you know I do linux for Microblaze and this is the right time to got some
ACK from community. I looked at Linus tree and 2.6.26 has been released and it
is the right time for Microblaze.
I have got ACK from John Williams (Petalogix.com) who starts with linux for
microblaze and Steve Neuendorffer from Xilinx (Xilinx is manufacturer of
Microblaze CPU).
I would like to got some ACK from people which are not directly connected with
Microblaze and who are interested in parts of linux.
I have sent some request to people who I know:
Jon Loeliger and David Gibson for ACK on generic DTS structure
Sam Ravnborg for Kconfig and Makefile ACK
Arnd: I hope you know much about microblaze. Could you help me with the last
stage of merging?
Could you recommend me people who can give me valuable ACK? (I'll send patches
to them and then full pack to LKML too).
Thanks for your help,
Michal Simek
next reply other threads:[~2008-07-14 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 9:18 Michal Simek [this message]
2008-07-14 11:24 ` Microblaze architecture - ACK Arnd Bergmann
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=487B19E0.3030301@seznam.cz \
--to=monstr@seznam.cz \
--cc=John.Linn@xilinx.com \
--cc=arnd@arndb.de \
--cc=david@gibson.dropbear.id.au \
--cc=jdl@jdl.com \
--cc=john.williams@petalogix.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=stephen.neuendorffer@xilinx.com \
--cc=torvalds@linux-foundation.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