All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Craig Shelley <craig@microtron.org.uk>
Subject: Re: linux-next: manual merge of the usb tree with the ttydev tree
Date: Wed, 3 Jun 2009 08:00:17 -0700	[thread overview]
Message-ID: <20090603150017.GD30890@kroah.com> (raw)
In-Reply-To: <20090603204655.3f431574.sfr@canb.auug.org.au>

On Wed, Jun 03, 2009 at 08:46:55PM +1000, Stephen Rothwell wrote:
> Hi Alan,
> 
> On Wed, 3 Jun 2009 09:55:47 +0100 Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> >
> > > As a side issue, the last patch has no SOB from Craig in the ttydev tree.
> > 
> > Yes it does...
> > 
> >     Signed-off-by: Craig Shelley <craig@microtron.org.uk>
> >     
> >     (Fixed some collisions merging)
> >     
> >     Signed-off-by: Alan Cox <alan@linux.intel.com>
> 
> Sorry, going blind in my old age :-)
> 
> > > So, I just used the ttydev tree version on the assumption that my
> > > reasoning above is correct.
> > 
> > and the ttydev tree one is the one to use
> 
> Thanks for the confirmation.

Ok, I'll drop these three patches from my tree.

thanks,

greg k-h

  reply	other threads:[~2009-06-03 15:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03  8:07 linux-next: manual merge of the usb tree with the ttydev tree Stephen Rothwell
2009-06-03  8:55 ` Alan Cox
2009-06-03 10:46   ` Stephen Rothwell
2009-06-03 15:00     ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-10  8:41 Stephen Rothwell
2009-06-10 10:06 ` Alan Cox
2009-06-10 11:09   ` Stephen Rothwell
2009-06-05  5:41 Stephen Rothwell
2009-06-05 17:42 ` Greg KH
2009-06-05  5:34 Stephen Rothwell
2009-06-05 17:42 ` Greg KH
2009-06-03  8:13 Stephen Rothwell
2009-06-03  7:55 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=20090603150017.GD30890@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=craig@microtron.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.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.