From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Zach Brown <zach.brown@oracle.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: Voyager, tty locking
Date: Tue, 08 Aug 2006 13:04:48 -0500 [thread overview]
Message-ID: <1155060288.26517.43.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <44D8D073.5080505@oracle.com>
On Tue, 2006-08-08 at 10:57 -0700, Zach Brown wrote:
> > The signal handling also appears to be incorrect as it does an
> > unprotected sigfillset that also appears unneccessary. As I don't have a
> > bowtie and am therefore not a qualified voyager maintainer I leave that
> > to James.
>
> Bowtie or not, you touched it last!
>
> This seems like a decent candidate for being moved over to the kthread API..
Alan's patch looks fine so you can add my ack to it (and that of my
bowtie).
I'll add the kthread conversion to my list ... unless the suggestor also
wants to become the implementor?
James
next prev parent reply other threads:[~2006-08-08 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 18:07 Alan Cox
2006-08-08 17:57 ` Zach Brown
2006-08-08 18:04 ` James Bottomley [this message]
2006-08-08 18:38 ` Zach Brown
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=1155060288.26517.43.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=zach.brown@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®