From: Greg KH <greg@kroah.com>
To: Michael Clark <michael@metaparadigm.com>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.0-test9 Fix oops in quirk_via_bridge
Date: Fri, 7 Nov 2003 09:46:59 -0800 [thread overview]
Message-ID: <20031107174659.GC1546@kroah.com> (raw)
In-Reply-To: <3FA23B77.5040804@metaparadigm.com>
On Fri, Oct 31, 2003 at 06:37:43PM +0800, Michael Clark wrote:
> On 10/31/03 18:00, Russell King wrote:
> >On Fri, Oct 31, 2003 at 05:58:39PM +0800, Michael Clark wrote:
> >
> >Your fix looks 99% correct, except for the "__devinitdata" part - if
> >you drop this and resubmit the patch, I'm sure gregkh will take it.
>
> Cool. dropped __devinitdata, tested and works. Now I can suspend
> and resume then insert my ieee1394 cardbus controller with no oops.
Thanks, I've applied this and will send it on to Linus in a bit.
greg k-h
prev parent reply other threads:[~2003-11-07 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 9:42 [PATCH] 2.6.0-test9 Fix oops in quirk_via_bridge Michael Clark
2003-10-31 9:49 ` Russell King
2003-10-31 9:58 ` Michael Clark
2003-10-31 10:00 ` Russell King
2003-10-31 10:37 ` Michael Clark
2003-11-07 17:46 ` Greg KH [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=20031107174659.GC1546@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@metaparadigm.com \
--cc=rmk+lkml@arm.linux.org.uk \
/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