First patch questions (target mailing list, target tree)

First patch questions (target mailing list, target tree)

[Wojciech Kudla]

Hi,

I'd like to send a patch to arch/x86/kernel/smp.c but I'm not sure about 
2 details:

1) which branch of whose tree do I crate the patch against?
According to MAINTAINERS:

M:      Thomas Gleixner <tglx@linutronix.de>
M:      Ingo Molnar <mingo@redhat.com>
R:      "H. Peter Anvin" <hpa@zytor.com>
M:      x86@kernel.org
L:      linux-kernel@vger.kernel.org
T:      git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 
x86/core

Is this the right branch and the correct tree?

2) how do I access archives of x86@kernel.org?

Thanks!


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: First patch questions (target mailing list, target tree)

[Konstantin Ryabitsev]

On Sun, May 10, 2020 at 06:26:27PM +0100, Wojciech Kudla wrote:

(I'll let others answer your first question.)

> 2) how do I access archives of x86@kernel.org?

You cannot, because this is an alias, not a mailing list. You can use 
query filters on LKML to see what public messages were sent to that 
alias, e.g.:

https://lore.kernel.org/lkml/?q=tc%3Ax86%40kernel.org+d%3A20200301..

However, using more precise queries may be more useful, as the above 
returns too many hits to be useful.

-K

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: First patch questions (target mailing list, target tree)

[Wojciech Kudla]

On 10/05/2020 19:12, Konstantin Ryabitsev wrote:
> On Sun, May 10, 2020 at 06:26:27PM +0100, Wojciech Kudla wrote:
> 
> (I'll let others answer your first question.)
> 
>> 2) how do I access archives of x86@kernel.org?
> 
> You cannot, because this is an alias, not a mailing list. You can use
> query filters on LKML to see what public messages were sent to that
> alias, e.g.:
> 
> https://lore.kernel.org/lkml/?q=tc%3Ax86%40kernel.org+d%3A20200301..
> 
> However, using more precise queries may be more useful, as the above
> returns too many hits to be useful.
> 
> -K
> 

The interface works but it's not very effective.
Is there any NNTP group I could subscribe to in order to get access to 
the full history, just like we have gmane.linux.kernel.kernelnewbies?
I don't mind pulling everything for multiple aliases. I can filter it in 
my NNTP client anyway.

Thanks


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: First patch questions (target mailing list, target tree)

[Wojciech Kudla]

On 10/05/2020 19:12, Konstantin Ryabitsev wrote:
> On Sun, May 10, 2020 at 06:26:27PM +0100, Wojciech Kudla wrote:
> 
> (I'll let others answer your first question.)
> 
>> 2) how do I access archives of x86@kernel.org?
> 
> You cannot, because this is an alias, not a mailing list. You can use
> query filters on LKML to see what public messages were sent to that
> alias, e.g.:
> 
> https://lore.kernel.org/lkml/?q=tc%3Ax86%40kernel.org+d%3A20200301..
> 
> However, using more precise queries may be more useful, as the above
> returns too many hits to be useful.
> 
> -K
> 

The interface works but it's not very effective.
Is there any NNTP group I could subscribe to in order to get access to 
the full history, just like we have gmane.linux.kernel.kernelnewbies?
I don't mind pulling everything for multiple aliases. I can filter it in 
my NNTP client anyway.

Thanks

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: First patch questions (target mailing list, target tree)

[Valdis Klētnieks]

[-- Attachment #1.1: Type: text/plain, Size: 1084 bytes --]

On Sun, 10 May 2020 18:26:27 +0100, Wojciech Kudla said:
> I'd like to send a patch to arch/x86/kernel/smp.c but I'm not sure about

> 1) which branch of whose tree do I crate the patch against?
> According to MAINTAINERS:

T:      git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git

There you go.   In general, you're usually OK using either the current Linus
tree or linux-next tree.  Unless you're doing work that directly intersects
with other development, those should be quite good enough.

Linus's tree:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

To add linux-next to that:
$ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
$ git fetch linux-next
$ git fetch --tags linux-next
... # later on
$ git remote update

Don't use 'git pull' against linux-next, because it's rebuilt every day.
Strange and wondrous things will happen.  That also means that you
can't git bisect between (say) next-20200405 and next-20200503 (though
you can bisect between a Linus v5.7-rc3 tag and a next- tag )


[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: First patch questions (target mailing list, target tree)

[Wojciech Kudla]

On 10/05/2020 23:55, Valdis Klētnieks wrote:
> On Sun, 10 May 2020 18:26:27 +0100, Wojciech Kudla said:
>> I'd like to send a patch to arch/x86/kernel/smp.c but I'm not sure about
> 
>> 1) which branch of whose tree do I crate the patch against?
>> According to MAINTAINERS:
> 
> T:      git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> 
> There you go.   In general, you're usually OK using either the current Linus
> tree or linux-next tree.  Unless you're doing work that directly intersects
> with other development, those should be quite good enough.
> 
> Linus's tree:
> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> 
> To add linux-next to that:
> $ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> $ git fetch linux-next
> $ git fetch --tags linux-next
> ... # later on
> $ git remote update
> 
> Don't use 'git pull' against linux-next, because it's rebuilt every day.
> Strange and wondrous things will happen.  That also means that you
> can't git bisect between (say) next-20200405 and next-20200503 (though
> you can bisect between a Linus v5.7-rc3 tag and a next- tag )
> 
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> 

This is exactly what I was looking for. Thank you!


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Re: First patch questions (target mailing list, target tree)

[Wojciech Kudla]

On 10/05/2020 23:55, Valdis Klētnieks wrote:
> On Sun, 10 May 2020 18:26:27 +0100, Wojciech Kudla said:
>> I'd like to send a patch to arch/x86/kernel/smp.c but I'm not sure about
> 
>> 1) which branch of whose tree do I crate the patch against?
>> According to MAINTAINERS:
> 
> T:      git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> 
> There you go.   In general, you're usually OK using either the current Linus
> tree or linux-next tree.  Unless you're doing work that directly intersects
> with other development, those should be quite good enough.
> 
> Linus's tree:
> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> 
> To add linux-next to that:
> $ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> $ git fetch linux-next
> $ git fetch --tags linux-next
> ... # later on
> $ git remote update
> 
> Don't use 'git pull' against linux-next, because it's rebuilt every day.
> Strange and wondrous things will happen.  That also means that you
> can't git bisect between (say) next-20200405 and next-20200503 (though
> you can bisect between a Linus v5.7-rc3 tag and a next- tag )
> 
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> 

This is exactly what I was looking for. Thank you!

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies