Re: linux-next: manual merge of the perfmon3 tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ingo,


On Tue, Nov 25, 2008 at 4:33 PM, Ingo Molnar <mingo@xxxxxxx> wrote:
>
> * stephane eranian <eranian@xxxxxxxxxxxxxx> wrote:
>
>> So I am not sure I understand your point about submitting the
>> changes to the x86 tree first.
>
> You are modifying x86 architecture files to enable a kernel feature on
> x86. Such feature enablement, if it's pushed into linux-next, must go
> via the arch maintainers.
>
> The x86 impact of the perfmon3 tree is substantial:
>
[snip]
>  25 files changed, 2340 insertions(+), 6 deletions(-)
>
> linux-next is not a development kernel - it is an integration tree
> simulating the next version of the upstream kernel and hence all trees
> that are in it must be synced up (and in this case, go via) their
> respective maintainers.
>
Perfmon3 as it exists in linux-next has two components: generic + x86
I can send x86@xxxxxxxxxx the x86 specific patches to integrate them into
the x86 tree even though they would not be operational without the generic part.
But then, where do I send the generic code?

> Thanks,
>
>        Ingo
>
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux