All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-next@vger.kernel.org,
	Jaswinder Singh <jaswinder@infradead.org>,
	Chas Williams <chas@cmf.nrl.navy.mil>,
	David Miller <davem@davemloft.net>
Subject: Re: linux-next: manual merge of the firmware tree
Date: Mon, 30 Jun 2008 19:33:13 +1000	[thread overview]
Message-ID: <20080630193313.0f00a764.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1214817853.10393.330.camel@pmac.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 719 bytes --]

Hi David,

On Mon, 30 Jun 2008 10:24:13 +0100 David Woodhouse <dwmw2@infradead.org> wrote:
>
> Oops, sorry -- I'd forgotten about that patch, and I let Jaswinder go
> ahead and do it again.
> 
> I think the reason I didn't apply the patch from Chas to my tree was
> because I'm trying to be very careful to preserve functionality -- when
> I ask Linus to pull the firmware tree, I still want people to be able to
> build in _all_ the firmware they could before.
> 
> I'm happy enough to see it done separately though; I'll drop our
> fore200e patch from the firmware-2.6.git tree.

OK, thanks.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-06-30  9:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30  9:09 linux-next: manual merge of the firmware tree Stephen Rothwell
2008-06-30  9:24 ` David Woodhouse
2008-06-30  9:33   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-28  5:03 Stephen Rothwell
2008-11-29  0:14 ` Divy Le Ray
2008-11-29  0:48   ` Stephen Rothwell
2008-11-29 10:11     ` David Woodhouse
2008-11-25  7:21 Stephen Rothwell
2008-10-15  7:58 Stephen Rothwell
2008-09-01  6:19 Stephen Rothwell
2008-08-28  5:38 Stephen Rothwell
2008-08-28 13:51 ` Takashi Iwai
2008-07-29  4:27 Stephen Rothwell
2008-07-11  6:02 Stephen Rothwell
2008-07-07 16:02 Stephen Rothwell
2008-06-30  9:17 Stephen Rothwell
2008-06-30  9:14 Stephen Rothwell
2008-06-26 13:38 Stephen Rothwell
2008-06-26 13:51 ` Takashi Iwai
2008-06-26 15:42   ` Stephen Rothwell
2008-06-26 15:47     ` David Woodhouse
2008-06-30  9:23 ` Stephen Rothwell
2008-06-30  9:27   ` David Woodhouse
2008-06-30  9:32     ` Stephen Rothwell
2008-06-24  6:55 Stephen Rothwell
2008-06-24  7:57 ` Stephen Rothwell
2008-06-24  8:04   ` David Woodhouse
2008-06-24 11:20     ` 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=20080630193313.0f00a764.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=chas@cmf.nrl.navy.mil \
    --cc=davem@davemloft.net \
    --cc=dwmw2@infradead.org \
    --cc=jaswinder@infradead.org \
    --cc=linux-next@vger.kernel.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.