public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell•net>
To: spi-devel-general@lists•sourceforge.net,
	Eric Miao <eric.y.miao@gmail•com>,
	Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Ned Forrester <nforrester@whoi•edu>, linux-next@vger•kernel.org
Subject: Re: [spi-devel-general] linux-next: manual merge of the pxa tree
Date: Wed, 24 Sep 2008 21:57:47 -0700	[thread overview]
Message-ID: <200809242157.47494.david-b@pacbell.net> (raw)
In-Reply-To: <f17812d70809152002p6df35c05o743d9d86fca37827@mail.gmail.com>

On Monday 15 September 2008, Eric Miao wrote:
> >> I fixed it up (see below) and can carry the fixup (though it could be
> >> fixed in the pxa tree in a merge with Linus' tree).  Please check the
> >> fixup.
> >
> > The last word I had from David Brownell, was that Eric should make his
> > patch fit after mine.  I think Eric was planning to re-submit, but maybe
> > you have saved him the trouble.  I will leave it to Eric to decide if
> > you fixed everything needed.
> >
> 
> I'll take off the patch to save Stephen's time on this. Sorry for the
> noise.

Uh, I have yet to see any version of this patch... could someone post
it so the SPI maintainer at least has a chance to look at it?

  reply	other threads:[~2008-09-25  5:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-14 19:27 linux-next: manual merge of the pxa tree Stephen Rothwell
     [not found] ` <20080915052750.0b0c924c.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-09-15 13:18   ` Ned Forrester
2008-09-16  3:02     ` Eric Miao
2008-09-25  4:57       ` David Brownell [this message]
2008-09-25  7:49         ` [spi-devel-general] " Eric Miao
     [not found]           ` <f17812d70809250049g3f3b86e7x12dab8cc4f8b1cd6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-25  8:20             ` David Brownell

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=200809242157.47494.david-b@pacbell.net \
    --to=david-b@pacbell$(echo .)net \
    --cc=eric.y.miao@gmail$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=nforrester@whoi$(echo .)edu \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=spi-devel-general@lists$(echo .)sourceforge.net \
    /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