From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] serial: fix struct uart_info change fallout
Date: Wed, 23 Jul 2008 02:22:24 +1000 [thread overview]
Message-ID: <20080723022224.22eb4d26.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080722165929.717e38d4@lxorguk.ukuu.org.uk>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
Hi Alan,
On Tue, 22 Jul 2008 16:59:29 +0100 Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>
> I really expected to get the rest merged within an hour or two, but then
> it broke, then I was travelling and each time I got wireless access to
> resync the tree and work on it - it broke again and again and again.
>
> Next time I will bump the patch up the pile and get it out earlier when
> that occurs.
Excellent.
Just asking: do you have an aversion for merging fixes back into
patches? Not a problem, just so I know. Different people work
differently.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-07-22 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 0:25 Stephen Rothwell
2008-07-22 0:38 ` Dave Jones
2008-07-22 1:34 ` Stephen Rothwell
2008-07-22 2:00 ` Alan Cox
2008-07-22 1:58 ` Alan Cox
2008-07-22 3:01 ` Stephen Rothwell
2008-07-22 10:44 ` Alan Cox
2008-07-22 15:49 ` Stephen Rothwell
2008-07-22 15:59 ` Alan Cox
2008-07-22 16:22 ` Stephen Rothwell [this message]
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=20080723022224.22eb4d26.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®