From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alan Cox <alan@lxorguk•ukuu.org.uk>
Cc: Greg KH <greg@kroah•com>,
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 20:46:55 +1000 [thread overview]
Message-ID: <20090603204655.3f431574.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090603095547.1641ca7b@lxorguk.ukuu.org.uk>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
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.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-06-03 10:47 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 [this message]
2009-06-03 15:00 ` Greg KH
-- 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=20090603204655.3f431574.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alan@lxorguk$(echo .)ukuu.org.uk \
--cc=craig@microtron$(echo .)org.uk \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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