From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bill Irwin <bill.irwin@oracle.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i386: fix suspend/resume with dynamically allocated irq stacks
Date: Wed, 02 May 2007 23:01:05 -0700 [thread overview]
Message-ID: <46397AA1.8090606@goop.org> (raw)
In-Reply-To: <20070503054809.GF26598@holomorphy.com>
Bill Irwin wrote:
> On Wed, May 02, 2007 at 06:56:09PM -0700, Jeremy Fitzhardinge wrote:
>
>> This fixes two bugs:
>> - the stack allocation must be marked __cpuinit, since it gets called
>> on resume as well.
>> - presumably the interrupt stack should be freed on unplug if its
>> going to get reallocated on every plug.
>> [ Only non-vmalloced stacks tested. ]
>> Signed-off-by: Jeremy Fitzhardinge <jeremy@xensource.com>
>> ---
>> arch/i386/kernel/irq.c | 42 +++++++++++++++++++++++++++++++++++++-----
>> 1 file changed, 37 insertions(+), 5 deletions(-)
>>
>
> Updated patch follows. Please add your Signed-off-by: if it meets your
> approval;
What does it apply to? I'm getting conflicts if I replace my patch with
this. Or does it replace one of your patches?
J
next prev parent reply other threads:[~2007-05-03 6:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 1:56 [PATCH] i386: fix suspend/resume with dynamically allocated irq stacks Jeremy Fitzhardinge
2007-05-03 2:25 ` Bill Irwin
2007-05-03 2:31 ` Bill Irwin
2007-05-03 5:48 ` Bill Irwin
2007-05-03 6:01 ` Jeremy Fitzhardinge [this message]
2007-05-03 6:12 ` Bill Irwin
2007-05-03 7:07 ` Jeremy Fitzhardinge
2007-05-03 7:39 ` Bill Irwin
2007-05-03 8:04 ` Bill Irwin
2007-05-03 6:41 ` Bill Irwin
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=46397AA1.8090606@goop.org \
--to=jeremy@goop.org \
--cc=bill.irwin@oracle.com \
--cc=linux-kernel@vger.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