From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Rambaldi <rambaldi@xs4all.nl>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.27-rc5 xen balloon driver warnings
Date: Mon, 08 Sep 2008 11:14:49 -0700 [thread overview]
Message-ID: <48C56B99.9020307@goop.org> (raw)
In-Reply-To: <20080908180126.GB29264@elte.hu>
Ingo Molnar wrote:
> * Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
>
>> Rambaldi wrote:
>>
>>> I used the complete patch, I had some compile warnings.
>>>
>> Well, the compile warning are bad news. Just use the first hunk.
>>
>> Ingo, could you send this up to Linus? It's a subset of a patch you've
>> already got in your tree.
>>
>
> i cherry-picked the whole thing as that's the tested commit. Is that
> fine too?
No, because it caused compile-time warnings. The signatures on sysfs
access functions changed, so that patch will break unless the rest of
the sysfs changes went in.
J
next prev parent reply other threads:[~2008-09-08 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 8:41 2.6.27-rc5 xen balloon driver warnings Rambaldi
2008-09-07 22:38 ` Jeremy Fitzhardinge
2008-09-08 15:37 ` Rambaldi
2008-09-08 16:54 ` Jeremy Fitzhardinge
2008-09-08 18:01 ` Ingo Molnar
2008-09-08 18:14 ` Jeremy Fitzhardinge [this message]
2008-09-08 18:21 ` Ingo Molnar
2008-09-08 17:59 ` Ingo Molnar
2008-09-08 18:13 ` Jeremy Fitzhardinge
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=48C56B99.9020307@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rambaldi@xs4all.nl \
/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;
as well as URLs for NNTP newsgroup(s).