linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jaswinder Singh <jaswinder@infradead.org>
Cc: Greg KH <greg@kroah.com>,
	linux-next@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: linux-next: manual merge of the usb tree
Date: Wed, 16 Jul 2008 17:45:25 +1000	[thread overview]
Message-ID: <20080716174525.310fb332.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1216192808.3394.12.camel@jaswinder.satnam>

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

Hi Jaswinder,

On Wed, 16 Jul 2008 12:50:08 +0530 Jaswinder Singh <jaswinder@infradead.org> wrote:
>
> On Wed, 2008-07-16 at 17:13 +1000, Stephen Rothwell wrote:
> 
> > What needs to happen is that Alan's patch needs to be redone based on
> > Linus' tree of today.
> > 
> 
> My patch is smaller and simpler as compare to Alan patch.

However, your patch is already in Linus' tree and Greg's problem is
getting his tree (which contains Alan's patch) into Linus' tree.

> So can we follow this approach for linux-next tree:-
> 
> 1. Remove my patch from Linus tree
> 2. Apply Alan patch first
> 3. Then I will give you firmware patch based upon yesterday tree which I
> installed here :-
> http://git.infradead.org/users/jaswinder/linux-next.git
> 4. Then you apply firmware patch

This is a lot more work for me (and I have limited time) and Alan's patch
still needs to be redone before it is merged into Linus' tree ...

The linus-next tree is not and end unto itself, it is merely a way to see
how things will end up in Linus' tree.

-- 
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-07-16  7:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16  2:02 linux-next: manual merge of the usb tree Stephen Rothwell
2008-07-16  2:30 ` Greg KH
2008-07-16  7:06 ` Jaswinder Singh
2008-07-16  7:13   ` Stephen Rothwell
2008-07-16  7:20     ` Jaswinder Singh
2008-07-16  7:45       ` Stephen Rothwell [this message]
2008-07-16  7:49         ` Jaswinder Singh
2008-07-16  7:58           ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2013-10-22 15:08 linux-next: Tree for Oct 22 Thierry Reding
2013-10-22 15:08 ` linux-next: manual merge of the usb tree Thierry Reding
2013-10-22 18:02   ` Srinivas Pandruvada
2008-11-10  1:06 Stephen Rothwell
2008-11-10  1:40 ` Greg KH
2008-10-14  3:53 Stephen Rothwell
2008-10-14  3:47 Stephen Rothwell
2008-10-14  3:37 Stephen Rothwell
2008-10-14  3:31 Stephen Rothwell
2008-10-14  5:44 ` Alexey Klimov
2008-10-14  3:27 Stephen Rothwell
2008-07-17  0:54 Stephen Rothwell
2008-07-17  7:04 ` Greg KH
2008-07-07  3:09 Stephen Rothwell
2008-07-07 14:09 ` Alan Stern
2008-07-07 16:09   ` 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=20080716174525.310fb332.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=greg@kroah.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).