From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Gokul Caushik <caushik1@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
Joe Millenbach <jmillenbach@gmail.com>
Subject: Re: bzImage 2.12
Date: Sun, 27 Jan 2013 11:39:13 -0800 [thread overview]
Message-ID: <0023b092-6149-418f-8adc-dd7f5631006c@email.android.com> (raw)
In-Reply-To: <CAE9FiQUFZwmiBgYwsoLZ4O+f_w-V01Eb8_6L4ZrHeA4DfLJd8A@mail.gmail.com>
I'm planning to sort it out... I'll let you know if I run out of bandwidth.
Yinghai Lu <yinghai@kernel.org> wrote:
>On Sun, Jan 27, 2013 at 11:19 AM, H. Peter Anvin <hpa@zytor.com> wrote:
>>
>> I think we can probably do that, since it doesn't affect anything
>non-broken
>> at this point. I'm sorting out what can be done for 3.8 vs 3.9 at
>this
>> point.
>>
>> Anyway, as you can tell I'm spending this weekend working for a
>reason.
>>
>> It turns out the patch I sent out doesn't actually build. Here is an
>> updated patch. Can I get your ack for this so I can do the
>appropriate
>> hacks to your and Yinghai's patchsets?
>
>Acked-by: Yinghai Lu <yinghai@kernel.org>
>
>Do you want to me to update my patchset on top it and resend?
>
>or you are going to sort it out by you self?
>
>Thanks
>
>Yinghai
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
next prev parent reply other threads:[~2013-01-27 19:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 19:02 H. Peter Anvin
2013-01-27 19:10 ` David Woodhouse
2013-01-27 19:19 ` H. Peter Anvin
2013-01-27 19:25 ` Matt Fleming
2013-01-27 19:38 ` Yinghai Lu
2013-01-27 19:39 ` H. Peter Anvin [this message]
2013-01-28 2:14 ` Yinghai Lu
2013-01-28 3:36 ` H. Peter Anvin
2013-01-29 3:50 ` Yinghai Lu
2013-01-29 4:22 ` Yinghai Lu
2013-01-29 19:36 ` Yinghai Lu
2013-01-27 22:08 ` David Woodhouse
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=0023b092-6149-418f-8adc-dd7f5631006c@email.android.com \
--to=hpa@zytor.com \
--cc=caushik1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jmillenbach@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.org \
/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
all inboxes | Powered by JetHome®