From: Ingo Molnar <mingo@elte•hu>
To: eranian@gmail•com
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org,
Alexander van Heukelum <heukelum@mailshack•com>,
the arch/x86 maintainers <x86@kernel•org>,
"H. Peter Anvin" <hpa@zytor•com>,
Thomas Gleixner <tglx@linutronix•de>,
Peter Zijlstra <a.p.zijlstra@chello•nl>,
Andrew Morton <akpm@linux-foundation•org>
Subject: Re: linux-next: manual merge of the perfmon3 tree
Date: Tue, 25 Nov 2008 17:51:18 +0100 [thread overview]
Message-ID: <20081125165118.GF22504@elte.hu> (raw)
In-Reply-To: <7c86c4470811250836k2f798c21pe4766a565a6231ab@mail.gmail.com>
* stephane eranian <eranian@googlemail•com> wrote:
> Ingo,
>
>
> On Tue, Nov 25, 2008 at 4:33 PM, Ingo Molnar <mingo@elte•hu> wrote:
> >
> > * stephane eranian <eranian@googlemail•com> 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@kernel•org 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?
There are a number of ways to do that - and we'll sure be able to work
that out - but first please submit the full patchset (x86 and generic
bits as well) to lkml with the x86 maintainers Cc:-ed.
In any case, until that happens and until there's agreement with the
x86 maintainers (there's none at the moment) the perfmon3 tree (or at
least its x86 bits) needs to be removed from linux-next. I already see
a number of problems with the patchset that we'll have to work out via
an iterative review process.
Ingo
next prev parent reply other threads:[~2008-11-25 16:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 10:03 linux-next: manual merge of the perfmon3 tree Stephen Rothwell
2008-11-25 10:22 ` Ingo Molnar
2008-11-25 14:40 ` stephane eranian
2008-11-25 15:33 ` Ingo Molnar
2008-11-25 16:36 ` stephane eranian
2008-11-25 16:51 ` Ingo Molnar [this message]
2008-11-26 3:00 ` Stephen Rothwell
2008-11-26 3:33 ` Ingo Molnar
2008-11-26 7:06 ` Paul Mackerras
2008-11-26 7:16 ` Ingo Molnar
2008-11-26 8:32 ` stephane eranian
2008-11-26 8:46 ` Ingo Molnar
2008-11-26 9:00 ` Andrew Morton
2008-11-26 9:31 ` Peter Zijlstra
2008-11-26 10:21 ` Ingo Molnar
2008-11-25 10:39 ` Alexander van Heukelum
2008-11-25 15:19 ` stephane eranian
-- strict thread matches above, loose matches on Subject: below --
2008-11-26 4:24 H. Peter Anvin
2008-11-25 10:03 Stephen Rothwell
2008-11-07 8:42 Stephen Rothwell
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=20081125165118.GF22504@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=a.p.zijlstra@chello$(echo .)nl \
--cc=akpm@linux-foundation$(echo .)org \
--cc=eranian@gmail$(echo .)com \
--cc=heukelum@mailshack$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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