From: Harvey Harrison <harvey.harrison@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Jesper Nilsson <jesper.nilsson@axis.com>
Subject: Re: [PATCH 03/23] cris: introduce asm/swab.h
Date: Tue, 06 Jan 2009 14:21:52 -0800 [thread overview]
Message-ID: <1231280512.25147.7.camel@brick> (raw)
In-Reply-To: <alpine.LFD.2.00.0901061409270.3057@localhost.localdomain>
On Tue, 2009-01-06 at 14:11 -0800, Linus Torvalds wrote:
>
> On Tue, 6 Jan 2009, Harvey Harrison wrote:
> >
> > Sure, I sent regular patches as a courtesy to Andrew in case he slurped
> > it up, but I can resend with -M -B if you're going to take it directly,
> > should I wait until I see the remaining 4 arches hit your tree, or will
> > you worry about the timing?
>
> I'm not sure worrying about the timing makes much sense, since the bigger
> worry is wanting to merge things in time for -rc1 - and that means having
> a few days to catch any gotcha's. If parisc/xtensa/cris is broken for a
> day or two, I don't consider that a problem.
I've seen the sparc pull request go by and will assume it will be in
your tree.
I will not send cris, xtensa, parisc and the removal patches (22-23) so these
arches don't get broken even for a few days and will send those three and the removal
patch as soon as they merged.
Cheers,
Harvey
prev parent reply other threads:[~2009-01-06 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 21:30 [PATCH 03/23] cris: introduce asm/swab.h Harvey Harrison
2009-01-06 21:59 ` Linus Torvalds
2009-01-06 22:04 ` Harvey Harrison
2009-01-06 22:11 ` Linus Torvalds
2009-01-06 22:19 ` Sam Ravnborg
2009-01-06 22:21 ` Harvey Harrison [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=1231280512.25147.7.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jesper.nilsson@axis.com \
--cc=linux-kernel@vger.kernel.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 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.