From: John Levon <movement@marcelothewonderpenguin.com>
To: linux-kernel@vger.kernel.org
Cc: jonathan@buzzard.org.uk
Subject: Re: [Patch] 2.5.34 IRQ Patch
Date: Mon, 9 Sep 2002 20:16:26 +0100 [thread overview]
Message-ID: <20020909191626.GA59685@compsoc.man.ac.uk> (raw)
In-Reply-To: <20020909120451.GA23868@comet>
On Mon, Sep 09, 2002 at 08:04:52AM -0400, James Blackwell wrote:
> A note to those that are a bit rough on kernel patch newbies.... submitting
> a kernel patch for the very first time is a rather intimidating experience
> so please don't chew my head off unless its absolutely necessary.
I didn't look at this particular case, but the fixes are generally
not as simple as just replacing them mechanically. You need to ensure
that things are still properly locked wrt the interrupt handler since
the semantics have changed. See the discussion in the mail archives
regards
john
--
"This *is* Usenet, after all, where virtually every conversation that goes on
is fairly ludicrous in the first place."
- Godwin's Law FAQ
next prev parent reply other threads:[~2002-09-09 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 12:04 [Patch] 2.5.34 IRQ Patch James Blackwell
2002-09-09 19:16 ` John Levon [this message]
2002-09-09 13:49 ` James Blackwell
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=20020909191626.GA59685@compsoc.man.ac.uk \
--to=movement@marcelothewonderpenguin.com \
--cc=jonathan@buzzard.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.