On Monday 07 January 2008, Michal Simek wrote:
> 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.
>
Adding the whole architecture tree will probably be too much for
a single reviewer and almost certainly too muc
Bryan Wu wrote:
> On Jan 7, 2008 7:29 PM, Michal Simek <[EMAIL PROTECTED]> wrote:
>> I checked whole code with checkpatch.pl script to avoid code violations.
>> I hope I resolve the most of coding style problems.
>
> Yes, passing checkpatch.pl is required by LKML.
checkpatch.pl only gives guidanc
Bryan Wu wrote:
> On Jan 8, 2008 4:49 PM, Pekka Enberg <[EMAIL PROTECTED]> wrote:
>> On Jan 8, 2008 10:28 AM, Bryan Wu <[EMAIL PROTECTED]> wrote:
>> > 1. Push patches to LKML when merge window open (2 weeks after a stable
>> > kernel version release, for example 2 weeks after 2.6.24 released)
>>
>>
On Jan 8, 2008 4:49 PM, Pekka Enberg <[EMAIL PROTECTED]> wrote:
> Hi Bryan,
>
> On Jan 8, 2008 10:28 AM, Bryan Wu <[EMAIL PROTECTED]> wrote:
> > 1. Push patches to LKML when merge window open (2 weeks after a stable
> > kernel version release, for example 2 weeks after 2.6.24 released)
>
> You shou
Hi Bryan,
On Jan 8, 2008 10:28 AM, Bryan Wu <[EMAIL PROTECTED]> wrote:
> 1. Push patches to LKML when merge window open (2 weeks after a stable
> kernel version release, for example 2 weeks after 2.6.24 released)
You shouldn't wait for the merge window to open to send patches for
review for the f
On Jan 7, 2008 7:29 PM, Michal Simek <[EMAIL PROTECTED]> wrote:
> 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.
>
Welcome to the home of kernel.
I remember B
Hi Ben,
I redesigned all files for microblaze cpu (xilinx fpga).
All code is FDT compatible.
For those who don't know, FDT is the flattened device-tree format used
nowadays on PowerPC, based on the open firmware device-tree.
I'm really happy to see that being picked up by another architecture
On Mon, 2008-01-07 at 21:29 +1000, Michal Simek wrote:
> Hi all,
>
> I redesigned all files for microblaze cpu (xilinx fpga).
> All code is FDT compatible.
For those who don't know, FDT is the flattened device-tree format used
nowadays on PowerPC, based on the open firmware device-tree.
I'm rea
On Mon, Jan 07, 2008 at 10:51:40PM +1000, Michal Simek wrote:
> Hi Sam,
>
> > It this code drop available somewhere?
>
> the code is based on Petalogix kernel. I reduce huge Kconfig file to
> necessary size. You'll see in patch or in web.
>
> A brief information about this kernel is at http://ww
Pekka Enberg wrote:
> On Jan 7, 2008 1:29 PM, Michal Simek <[EMAIL PROTECTED]> wrote:
>> How many maintainers are acceptable? (one or more)
>
> You can have as many maintainers as you want but you probably don't
> want to make it too many.
Bug reporters and patch submitters shouldn't be required
Jan Engelhardt wrote:
On Jan 7 2008 18:26, Stefan Richter wrote:
Jan Engelhardt wrote:
On Jan 7, 2008 1:29 PM, Michal Simek <[EMAIL PROTECTED]> wrote:
Is it possible to create git repository in git.kernel.org for Microblaze
cpu?
...
Alternatively, providing your own git service is just as ef
On Jan 7 2008 18:26, Stefan Richter wrote:
>Jan Engelhardt wrote:
>>>On Jan 7, 2008 1:29 PM, Michal Simek <[EMAIL PROTECTED]> wrote:
Is it possible to create git repository in git.kernel.org for Microblaze
cpu?
>...
>> Alternatively, providing your own git service is just as effective,
>
Jan Engelhardt wrote:
>>On Jan 7, 2008 1:29 PM, Michal Simek <[EMAIL PROTECTED]> wrote:
>>> Is it possible to create git repository in git.kernel.org for Microblaze
>>> cpu?
...
> Alternatively, providing your own git service is just as effective,
> and comes with much more freedom :)
It is /almos
On Jan 7 2008 14:47, Pekka Enberg wrote:
>Hi Michael,
>
>On Jan 7, 2008 1:29 PM, Michal Simek <[EMAIL PROTECTED]> wrote:
>> Is it possible to create git repository in git.kernel.org for Microblaze
>> cpu?
>
>You need to ask the kernel.org administrators for that:
>
> http://www.kernel.org/faq/#ac
Hi Michal,
On Jan 7, 2008 3:00 PM, Michal Simek <[EMAIL PROTECTED]> wrote:
> > You can have as many maintainers as you want but you probably don't
> > want to make it too many. There aren't any "official" responsibilities
> > as a maintainer, it really depends on how much time and effort you're
>
Hi Pekka,
Is it possible to create git repository in git.kernel.org for Microblaze
cpu?
You need to ask the kernel.org administrators for that:
http://www.kernel.org/faq/#account
Thanks.
How many maintainers are acceptable? (one or more)
You can have as many maintainers as you want bu
Hi Sam,
> It this code drop available somewhere?
the code is based on Petalogix kernel. I reduce huge Kconfig file to
necessary size. You'll see in patch or in web.
A brief information about this kernel is at http://www.monstr.eu/fdt/
> I would like to review the Makefiles and to a lesser exte
Hi Michael,
On Jan 7, 2008 1:29 PM, Michal Simek <[EMAIL PROTECTED]> wrote:
> Is it possible to create git repository in git.kernel.org for Microblaze
> cpu?
You need to ask the kernel.org administrators for that:
http://www.kernel.org/faq/#account
On Jan 7, 2008 1:29 PM, Michal Simek <[EMAIL
On Mon, Jan 07, 2008 at 09:29:40PM +1000, Michal Simek wrote:
> Hi all,
>
> I redesigned all files for microblaze cpu (xilinx fpga).
> All code is FDT compatible.
Hi Michal.
It this code drop available somewhere?
I would like to review the Makefiles and to a lesser extent
the Kconfig files.
I c
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 repositor
20 matches
Mail list logo
