From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Tomas Hlavacek <tmshlvck@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: tty: WARNING at drivers/base/core.c:196 device_release()
Date: Thu, 6 Sep 2012 19:46:13 -0700 [thread overview]
Message-ID: <20120907024613.GA28505@kroah.com> (raw)
In-Reply-To: <20120907022928.GA14646@localhost>
On Fri, Sep 07, 2012 at 10:29:28AM +0800, Fengguang Wu wrote:
> Hi Tomas,
>
> FYI, this commit triggers a boot time warning.
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-next
> head: 6915c0e487c822e2436683e14302c0b8a6155cc7
> commit: 6915c0e487c822e2436683e14302c0b8a6155cc7 [1/1] tty: uartclk value from serial_core exposed to sysfs
Should now be fixed in my tree with a later patch, from Tomas, right?
thanks,
greg k-h
next prev parent reply other threads:[~2012-09-07 2:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 2:29 tty: WARNING at drivers/base/core.c:196 device_release() Fengguang Wu
2012-09-07 2:46 ` Greg Kroah-Hartman [this message]
2012-09-07 3:26 ` Fengguang Wu
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=20120907024613.GA28505@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmshlvck@gmail.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