DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=vystxuU9+DX37z7mdQTrUAPZiL7q+FPvE+7LPY1gcauvbGOVrx3LWKIKklfZIqvQlu
         nFY/gAkzKBMQpQKM+wouRgJKvSr9fpxz74xSfPg4ovMT4t8epuwb8DGAKmfSWGYqjbuZ
         gEUhEGXW8B4Ipp+mYfmRiJIuAlouilRf3SoeE=
MIME-Version: 1.0
In-Reply-To: <201008070954.08613.arnd@arndb.de>
References: <20100807192122.2005c856@tom-lei>
	<201008070954.08613.arnd@arndb.de>
Date: Sat, 7 Aug 2010 16:35:34 +0800
Message-ID: <AANLkTi=J9OpOcsGH1nGqu5O2O3TRGit3Lh=QUQL_u6Er@mail.gmail.com>
Subject: Re: TTY: warning in tty_lock on 2.6.35+gregkh tree
From: Ming Lei <tom.leiming@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 780
Lines: 22

2010/8/7 Arnd Bergmann <arnd@arndb.de>:
> On Saturday 07 August 2010, Ming Lei wrote:
>> Following the ttty warning during kernel boot, seems it is for a long time
>> in gregkh's tree.
>
> The fix for this is in the bkl/core tree, meaning it doesn't show up
> in the linux-next tree.
>
> The warning by itself is harmless, so there was no strict need to
> coordinate this better. In fact, with the removal of the optional
> BKL behavior, I believe the warning is now gone from the tty
> tree as well.

Oh, I see, thanks.

-- 
Lei Ming
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/