From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
James Simmons <jsimmons@infradead.org>
Subject: Re: [Linux-fbdev-devel] [PATCH] VT locking
Date: Wed, 07 Jan 2004 10:08:49 +1100 [thread overview]
Message-ID: <1073430528.4067.27.camel@gaston> (raw)
In-Reply-To: <20040106140002.6806757b.akpm@osdl.org>
> That's OK, it's just in there for a soak-test at present - this stuff is
> quite a long way away, yes?
The VT locking on the debug crude hack ? :)
Well it depends :) If nobody complains, it could get in pretty fast :)
In any case, please report me any trigger of the WARN_ON... I didn't
chield everything yet with the console sem, so there may still be
some of them coming from the low level code.
> It's probably just easiest for you to work against current -bk, send me a
> single rolled up patch whenever you have new things for people to test.
> When we're happy with it all we can do a bk merge of everything.
Ok.
prev parent reply other threads:[~2004-01-06 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 0:33 [PATCH] VT locking Benjamin Herrenschmidt
2004-01-06 12:16 ` Pavel Machek
2004-01-06 16:31 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-01-06 21:44 ` Benjamin Herrenschmidt
2004-01-06 22:00 ` Andrew Morton
2004-01-06 23:08 ` Benjamin Herrenschmidt [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=1073430528.4067.27.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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