From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, tglx@linutronix.de,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/3] x86, intel: Output microcode revision v5
Date: Wed, 12 Oct 2011 10:45:25 +0200 [thread overview]
Message-ID: <20111012084523.GB27853@elte.hu> (raw)
In-Reply-To: <20111011152050.GE14482@one.firstfloor.org>
* Andi Kleen <andi@firstfloor.org> wrote:
> On Mon, Oct 10, 2011 at 09:00:44AM +0200, Ingo Molnar wrote:
> >
> > Andi,
> >
> > If you want me to apply these patches then they need to be reviewed
> > and signed off by someone else who i trust and who i'm taking patches
> > from.
>
> Ingo,
>
> There's noone else to sign off because noone else is writing the
> patches.
The typical way of how such maintainer requests are solved is that
you'll have to find someone who is willing and able to work with you
on this topic, and who is willing to forward your patches to me or to
the other x86 maintainers (or any of the submaintainers we pull
from). It's not hard, we get and accept a lot of indirect patches.
Arguably i've already invested more time into this than i should
have, this direct approach clearly does not work and i cannot trust
you.
Thanks,
Ingo
prev parent reply other threads:[~2011-10-12 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 23:19 [PATCH 1/3] x86, intel: Output microcode revision v5 Andi Kleen
2011-09-28 23:19 ` [PATCH 2/3] x86, intel: Use cpu_update for Atom errata check Andi Kleen
2011-09-28 23:19 ` [PATCH 3/3] coretemp: Get microcode revision from cpu_data v2 Andi Kleen
2011-10-10 7:00 ` [PATCH 1/3] x86, intel: Output microcode revision v5 Ingo Molnar
2011-10-11 15:20 ` Andi Kleen
2011-10-12 8:45 ` Ingo Molnar [this message]
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=20111012084523.GB27853@elte.hu \
--to=mingo@elte.hu \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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