From: Peter Hurley <peter@hurleysoftware.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Jiri Slaby <jslaby@suse.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: WARNING: at drivers/tty/tty_buffer.c:476 (tty is NULL)
Date: Mon, 11 Feb 2013 21:53:58 -0500 [thread overview]
Message-ID: <1360637638.4415.13.camel@thor.lan> (raw)
In-Reply-To: <20130212020039.GA8979@concordia>
On Tue, 2013-02-12 at 13:00 +1100, Michael Ellerman wrote:
> Sorry I just mean I'm seeing the warning, I have no idea how.
Ok, no problem. I just got a little excited because that area of code
was hard to test adequately.
> > Can you reproduce after using the following patch series?
> > [PATCH v3 00/23] ldisc fixes
>
> What are they against? I tried Linus' tree and linux-next but they
> didn't apply cleanly against either.
The series was generated against next-20130204. 13/23 doesn't apply
cleanly at next-20130211 because of changes since. Rebases fine
though :)
The series is currently in mid-review, so a new series won't be out
until that completes. (Besides, next-20130211 doesn't even boot for
me.)
Regards,
Peter Hurley
next prev parent reply other threads:[~2013-02-12 2:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 15:37 WARNING: at drivers/tty/tty_buffer.c:476 (tty is NULL) Dave Jones
2013-01-18 20:53 ` Dave Jones
2013-01-18 21:07 ` Greg Kroah-Hartman
2013-01-19 21:00 ` Jiri Slaby
2013-01-30 18:33 ` Peter Hurley
2013-02-11 2:44 ` Michael Ellerman
2013-02-11 14:42 ` Peter Hurley
2013-02-12 2:00 ` Michael Ellerman
2013-02-12 2:53 ` Peter Hurley [this message]
2013-02-12 6:41 ` Michael Ellerman
2013-02-12 11:34 ` Peter Hurley
2013-02-17 6:26 ` Shawn Guo
2013-02-17 6:26 ` Shawn Guo
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=1360637638.4415.13.camel@thor.lan \
--to=peter@hurleysoftware.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
/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.