From: Andrew Morton <akpm@osdl.org>
To: Michael Frank <mflt1@micrologica.com.hk>
Cc: rmk@arm.linux.org.uk, daniel.ritz@gmx.ch,
linux-kernel@vger.kernel.org, linux-pcmcia@lists.infradead.org
Subject: Re: 2.5.74-mm3 yenta-socket oops back
Date: Thu, 10 Jul 2003 00:56:10 -0700 [thread overview]
Message-ID: <20030710005610.62dfa7ef.akpm@osdl.org> (raw)
In-Reply-To: <200307101448.58180.mflt1@micrologica.com.hk>
Michael Frank <mflt1@micrologica.com.hk> wrote:
>
> Is called from interrupt handler. Seems that events occur before the
> thread is created.
OK, fair enough. The interrupt probe happens before the socket
registration. It needs a /* comment */
next prev parent reply other threads:[~2003-07-10 7:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 22:39 yenta-socket oops with 2.5.73-mm3, 2.5.74, 2.5.74-mm1 Daniel Ritz
2003-07-06 3:26 ` Michael Frank
2003-07-06 7:45 ` Russell King
2003-07-06 13:14 ` Michael Frank
2003-07-06 22:15 ` Russell King
2003-07-07 2:02 ` Michael Frank
2003-07-10 3:27 ` 2.5.74-mm3 yenta-socket oops back Michael Frank
2003-07-10 4:30 ` Andrew Morton
2003-07-10 7:09 ` Michael Frank
2003-07-10 7:56 ` Andrew Morton [this message]
2003-07-10 10:08 ` Russell King
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=20030710005610.62dfa7ef.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=daniel.ritz@gmx.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=mflt1@micrologica.com.hk \
--cc=rmk@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