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: Wed, 26 Nov 2008 09:46:04 +0100 [thread overview]
Message-ID: <20081126084604.GN26036@elte.hu> (raw)
In-Reply-To: <7c86c4470811260032n64d69b04w5762e5f6cbd0cff9@mail.gmail.com>
* stephane eranian <eranian@googlemail•com> wrote:
> > We know and knew about the existence of the perfmon patches, but
> > they were always in the vague RFC category and never directly
> > submitted or Cc:-ed to us.
>
> As Stephen pointed out, the full patchset was posted on LKML in
> October I never saw any comments from you or any other x86
> maintainers. I always assumed you were ALL on LKML anyway.
There's nothing to be "pointed out" about that - i was well aware of
the regular perfmon spam on lkml ;-)
What was done in stealth was its sudden "will go upstream in 1-2
months" status change, and its showing up in linux-next. There was
ample opportunity to Cc: the maintainers for all of those steps - when
you sent the tree setup request to Stephen, etc.
Really, in such cases you are expected to ping the respective
maintainers about what they think about it and whether there's any
objections. If they only notice it via conflicts of problem patches in
linux-next they'll (rightfully) go into grumpy mode. _Especially_ if
then the linux-next integrator also plays stupid about basic kernel
workflow questions ;-)
> I have reposted the full patchset yesterday on LKML but
> unfortunately my script dropped the cc-list. I will repost today
> making sure x86@kernel•org is cc'ed. I am sorry about that, it never
> was intentional. I will be waiting for your feedback on the x86
> code.
ok, thanks. That's all that is needed normally.
Ingo
next prev parent reply other threads:[~2008-11-26 8:46 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
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 [this message]
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=20081126084604.GN26036@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