linux-kernel - New linux arch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <47820D24.3060800@fel.cvut.cz>
Date:	Mon, 07 Jan 2008 21:29:40 +1000
From:	Michal Simek <simekm2@....cvut.cz>
To:	linux-kernel@...r.kernel.org
CC:	monstr@...str.eu
Subject: New linux arch

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/