From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Dave Jones <davej@redhat.com>,
Randy Dunlap <rdunlap@xenotime.net>,
Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
Richard Hughes <hughsient@gmail.com>,
Julian Sikorski <belegdol@gmail.com>, Andi Kleen <ak@suse.de>
Subject: Re: [PATCH} x86_64 PM_TRACE support.
Date: Thu, 31 May 2007 17:43:06 +1000 [thread overview]
Message-ID: <1180597386.6777.59.camel@nigel.suspend2.net> (raw)
In-Reply-To: <20070530170921.e793a34f.randy.dunlap@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1744 bytes --]
Hi.
On Wed, 2007-05-30 at 17:09 -0700, Randy Dunlap wrote:
> > On Sat, May 26, 2007 at 04:32:54PM +1000, Nigel Cunningham wrote:
> >
> > Hi Nigel,
> >
> > > As promised I took another look at the patch and at what Randy had
> > > prepared to fix the IA64 compilation error. I did some more work on it,
> > > and believe that the following is the tidiest correct solution I can
> > > come up with. It differs from the version that caused the compilation
> > > error primarily in that:
> > >
> > > * the #include <asm/resume-trace.h> is inside the #ifdef
> > > CONFIG_PM_TRACE.
> > > * now-unnecessary protection for multiple #includes and ifdef testing of
> > > CONFIG_PM_TRACE in the asm code were removed.
> > > * do-nothing definitions for !PM_TRACE restored to
> > > include/linux/resume-trace.h.
> > >
> > > We're therefore depending upon kernel/power/Kconfig having the right
> > > depends condition. As far as I can see, IA64 doesn't define CONFIG_X86.
> > > Is that correct, or do we need to have (X86 && !IA64)?
> >
> > Can you post a copy of this that isn't mangled by quoted-printable encoding?
> > Whilst it looks fine in my MUA, the diff ends up looking like..
>
> yep :(
>
> http://www.xenotime.net/linux/patches/x8664-pm-trace-support.patch
>
> in case Nigel is asleep.
Thanks Randy. I wasn't asleep, but was out for most of the day.
> > I'm beginning to think we really need a Documentation/Unhorking-MUAs-HOWTO
> > judging by the amount of broken encodings we seem to get to lkml these days.
That would be good. I just took a look through evo's settings, but can't
find whatever option is set wrong. I think it's devolved on me :\.
Regards,
Nigel
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-05-31 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 6:32 [PATCH} x86_64 PM_TRACE support Nigel Cunningham
2007-05-27 20:39 ` Pavel Machek
2007-05-27 21:10 ` Julian Sikorski
2007-05-27 21:54 ` Nigel Cunningham
2007-05-27 21:53 ` Randy Dunlap
2007-05-31 0:01 ` Dave Jones
2007-05-31 0:09 ` Randy Dunlap
2007-05-31 7:43 ` Nigel Cunningham [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=1180597386.6777.59.camel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=belegdol@gmail.com \
--cc=davej@redhat.com \
--cc=hughsient@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rdunlap@xenotime.net \
/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