LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kay Sievers <kay.sievers@vrfy.org>,
	Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: build warnings after merge of the tty tree
Date: Sun, 9 Jan 2011 21:49:47 -0800	[thread overview]
Message-ID: <20110110054947.GA21969@kroah.com> (raw)
In-Reply-To: <20110110125908.4251eb45.sfr@canb.auug.org.au>

On Mon, Jan 10, 2011 at 12:59:08PM +1100, Stephen Rothwell wrote:
> Hi Greg,
> 
> On Sun, 9 Jan 2011 16:56:01 -0800 Greg KH <greg@kroah.com> wrote:
> >
> > Yes, Kay just sent me a patch to fix this, which I will queue up after
> > .38-rc1 is out.
> 
> It is surely a pretty obvious patch, why not just do a quick test and
> send it on to Linus (or at least your tty-current tree)?
> 
> /me gets annoyed by more warnings than necessary - especially when they
> should have never been introduced in the first place.

Sorry, I try to keep patches that were not in -next from getting into
Linus's tree before -rc1, but you are right, this should be fixed.  I'll
forward it on later this week, or bundle it up in the "move tty drivers
around" patch that I have for Linus right after -rc1 is out.

thanks,

greg k-h

  reply	other threads:[~2011-01-10  5:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21  7:11 Stephen Rothwell
2010-12-21 19:42 ` Greg KH
2011-01-10  0:49   ` Stephen Rothwell
2011-01-10  0:51     ` Kay Sievers
2011-01-10  0:56     ` Greg KH
2011-01-10  1:59       ` Stephen Rothwell
2011-01-10  5:49         ` Greg KH [this message]
2011-01-10 14:55         ` Kay Sievers
2015-03-10  5:37 Stephen Rothwell
2018-03-15  6:43 Stephen Rothwell
2018-03-15 17:34 ` Greg KH
2022-05-10 21:58 Stephen Rothwell
2022-05-10 22:46 ` Maciej W. Rozycki
2022-05-11  5:32   ` Greg KH
2022-05-13 22:47     ` Maciej W. Rozycki
2022-06-14  6:47 Stephen Rothwell

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=20110110054947.GA21969@kroah.com \
    --to=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: linux-next: build warnings after merge of the tty tree' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).