From: Greg KH <greg@kroah.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ub: oops with preempt ("Sahara Workshop")
Date: Wed, 24 Nov 2004 15:26:59 -0800 [thread overview]
Message-ID: <20041124232659.GI4394@kroah.com> (raw)
In-Reply-To: <20041123100247.2ea47e2d@lembas.zaitcev.lan>
On Tue, Nov 23, 2004 at 10:02:47AM -0800, Pete Zaitcev wrote:
> I admit that the code should be locked properly instead, but the global plan
> is to drop all P3 tagged printks anyway. So let it be guarded for the moment.
>
> Signed-off-by: Pete Zaitcev <zaitcev@yahoo.com>
Applied, thanks.
greg k-h
next prev parent reply other threads:[~2004-11-25 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 18:02 ub: oops with preempt ("Sahara Workshop") Pete Zaitcev
2004-11-24 23:26 ` Greg KH [this message]
2004-11-27 21:38 ` ub: oops with preempt ("Sahara Workshop") [u] Martin Schlemmer [c]
2004-11-28 0:55 ` Pete Zaitcev
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=20041124232659.GI4394@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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.