From: Greg KH <gregkh@linuxfoundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] tty changes for the locking warnings.
Date: Tue, 29 May 2012 18:32:31 +0900 [thread overview]
Message-ID: <20120529093231.GA19992@kroah.com> (raw)
In-Reply-To: <20120528131358.793c127e@pyramind.ukuu.org.uk>
On Mon, May 28, 2012 at 01:13:58PM +0100, Alan Cox wrote:
> On Mon, 28 May 2012 20:29:06 +0900
> Greg KH <greg@kroah.com> wrote:
>
> > On Mon, May 28, 2012 at 10:48:37AM +0100, Alan Cox wrote:
> > > Fix the tty locking warnings. This doesn't include the patches to the
> > > lock markup as I'm not sure which are the final valid ones there.
> >
> > So this should take care of the issues people have reported? Or are
> > Peter's patches still needed?
>
>
> These fix all the known actual locking issues. I'm not clear if one of
> the other various mark up patches are also needed to babysit the lockdep
> analyser
Ok, great, thanks for fixing this up.
But, it turns out I don't think I'll have internet access at all for the
next 4 days, due to travel arrangements, so can you send these directly
to Linus before 3.5-rc1 is out so they get in and we don't see a zillion
people complaining about it?
Feel free to add:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
to them.
thanks,
greg k-h
prev parent reply other threads:[~2012-05-29 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 9:48 [PATCH 0/2] tty changes for the locking warnings Alan Cox
2012-05-28 9:49 ` [PATCH 1/2] pty: Fix lock inversion Alan Cox
2012-05-28 9:49 ` [PATCH 2/2] tty: fix ldisc lock inversion trace Alan Cox
2012-05-28 11:29 ` [PATCH 0/2] tty changes for the locking warnings Greg KH
2012-05-28 12:13 ` Alan Cox
2012-05-29 9:32 ` Greg KH [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=20120529093231.GA19992@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@lxorguk.ukuu.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.