From: Michal Simek <simekm2@fel.cvut.cz>
To: linux-kernel@vger.kernel.org
Cc: monstr@monstr.eu
Subject: New linux arch
Date: Mon, 07 Jan 2008 21:29:40 +1000 [thread overview]
Message-ID: <47820D24.3060800@fel.cvut.cz> (raw)
Hi all,
I redesigned all files for microblaze cpu (xilinx fpga).
All code is FDT compatible.
I would like to ask you what is the best way to push these changes to
kernel.org.
I would like to know step by step how to do.
I have some question about.
I have changes in my internal git repository. I don't have public git
repository.
Is it possible to create git repository in git.kernel.org for Microblaze
cpu?
What are maintainers responsibilities? Do you have any page about?
I am U-BOOT maintainer at denx.de and I hope that the responsibilities
will be similar.
How many maintainers are acceptable? (one or more)
I checked whole code with checkpatch.pl script to avoid code violations.
I hope I resolve the most of coding style problems.
I see the right way to push all changes to public git repository and
then send patches in small logical group to LKML with CC to people from
microblaze community.
And then wait for comments from you, solve problems, update git
repository and send changes again.
Thanks for your comments.
Cheers,
Michal Simek
next reply other threads:[~2008-01-07 11:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 11:29 Michal Simek [this message]
2008-01-07 12:34 ` New linux arch Sam Ravnborg
2008-01-07 12:51 ` Michal Simek
2008-01-07 19:16 ` Sam Ravnborg
2008-01-07 12:47 ` Pekka Enberg
2008-01-07 13:00 ` Michal Simek
2008-01-07 13:12 ` Pekka Enberg
2008-01-07 13:34 ` Jan Engelhardt
2008-01-07 17:26 ` Stefan Richter
2008-01-07 17:39 ` Jan Engelhardt
2008-01-07 17:54 ` H. Peter Anvin
2008-01-07 18:20 ` Stefan Richter
2008-01-07 22:00 ` Benjamin Herrenschmidt
2008-01-07 22:39 ` Michal Simek
2008-01-08 8:28 ` Bryan Wu
2008-01-08 8:49 ` Pekka Enberg
2008-01-08 9:00 ` Bryan Wu
2008-01-08 17:05 ` Stefan Richter
2008-01-08 17:12 ` Stefan Richter
2008-01-09 1:16 ` 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=47820D24.3060800@fel.cvut.cz \
--to=simekm2@fel.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
/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