From: Michal Simek <michal.simek@petalogix•com>
To: linux-next@vger•kernel.org,
Stephen Rothwell <sfr@canb•auug.org.au>,
lkml <linux-arch@vger•kernel.org>
Subject: Microblaze arch merging
Date: Tue, 17 Mar 2009 10:01:30 +0100 [thread overview]
Message-ID: <49BF66EA.9030101@petalogix.com> (raw)
Hi Stephen and others,
I am preparing first pack for Microblaze CPU (If you want to review I
can send bunch of patches very soon).
This pack was reviewed in past on LKML and of course I have done some
changes there and move to latest kernel code.
Could you tell me what the right way is for adding to Microblaze code to
linux-next for testing and merging?
I don't expect that microblaze code break any other arch because all the
code is in arch/microblaze folder + some minor changes in
Kconfig for drivers.
We have ready git server for pushing too.
What is the best way for you? Code based on current linus-head on based
on linux-next?
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
next reply other threads:[~2009-03-17 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 9:01 Michal Simek [this message]
2009-03-17 12:26 ` Microblaze arch merging Stephen Rothwell
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=49BF66EA.9030101@petalogix.com \
--to=michal.simek@petalogix$(echo .)com \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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