public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
	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, 6 Jan 2009 23:19:52 +0100	[thread overview]
Message-ID: <20090106221952.GD23838@uranus.ravnborg.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0901061409270.3057@localhost.localdomain>

On Tue, Jan 06, 2009 at 02:11:43PM -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. 

mn10300, frv and maybe h8300 are waiting for these patches to hit mainline
before they move their headers to arch/$ARCH/include

So sooner is better so we can get the rest fixed in this respect.

For m68k I have sent a patch to unify the headers for m68k and m68knommu
in arch/m68k/include/...

I really hope it is heading towards you soon.

	Sam

  reply	other threads:[~2009-01-06 22:36 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 [this message]
2009-01-06 22:21       ` Harvey Harrison

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=20090106221952.GD23838@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=harvey.harrison@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox