From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-next@vger.kernel.org
Subject: Re: linux-next: ttydev tree build failure
Date: Tue, 1 Jul 2008 08:27:04 -0700 [thread overview]
Message-ID: <20080701152704.GB3973@kroah.com> (raw)
In-Reply-To: <20080702005134.d07261ad.sfr@canb.auug.org.au>
On Wed, Jul 02, 2008 at 12:51:34AM +1000, Stephen Rothwell wrote:
> Hi Alan,
>
> On Tue, 1 Jul 2008 15:23:02 +0100 Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> >
> > > It could easily (probably) have been the merge.
> > >
> > > I have reverted the ttydev tree for now. I am not sure quite where we go
> > > from here.
> >
> > Well I expected there would be a few explosions from merging a large new
> > tree in. No problem. As soon as the new tree is done and out I will
> > regenerate the patch set versus that which should iron out all the
> > firmware clashes and the like.
>
> One downsides of the way linux-next works is that, because it is
> recreated every day, you cannot really base anything on it that is to be
> merged into it.
>
> I really need to think about this when I am awake :-(
As there were a lot of merge issues with my tree, I don't mind putting
this in my queue if needed.
I had started to merge it in, and handled lots of these merge issues in
my tree pretty easily, so if needed, I can put it all back in there to
help with this problem.
thanks,
greg k-h
next prev parent reply other threads:[~2008-07-01 15:31 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 14:17 linux-next: ttydev tree build failure Stephen Rothwell
2008-07-01 14:23 ` Alan Cox
2008-07-01 14:51 ` Stephen Rothwell
2008-07-01 15:27 ` Greg KH [this message]
2008-07-01 15:36 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2008-07-02 5:08 Stephen Rothwell
2008-07-02 8:05 ` Alan Cox
2008-07-02 5:19 Stephen Rothwell
2008-07-02 5:21 ` Stephen Rothwell
2008-07-02 8:09 ` Alan Cox
2008-07-02 5:30 Stephen Rothwell
2008-07-02 18:10 ` Randy Dunlap
2008-07-02 19:54 ` Alan Cox
2008-07-18 8:59 Stephen Rothwell
2008-07-18 21:34 Aleksey Gorelov
2008-07-23 7:17 Stephen Rothwell
2008-07-23 12:39 ` Geert Uytterhoeven
2008-07-23 14:46 ` Alan Cox
2008-07-23 15:49 ` Geert Uytterhoeven
2008-07-23 15:47 ` Alan Cox
2008-07-23 16:39 ` Geert Uytterhoeven
2008-07-23 16:28 ` Alan Cox
2008-07-23 18:55 ` Geert Uytterhoeven
2008-08-20 8:23 Stephen Rothwell
2008-08-20 8:26 ` Alan Cox
2008-08-20 9:08 ` Stephen Rothwell
2008-09-02 7:23 Stephen Rothwell
2008-09-02 9:22 ` Alan Cox
2008-10-15 9:39 Stephen Rothwell
2008-10-20 8:06 Stephen Rothwell
2008-10-20 21:48 ` Lee Howard
2008-10-21 9:33 ` Alan Cox
2008-10-23 6:29 Stephen Rothwell
2008-10-23 6:29 ` Stephen Rothwell
2008-10-23 7:34 ` Alan Cox
2008-10-23 7:34 ` Alan Cox
2008-10-23 7:35 ` Benjamin Herrenschmidt
2008-10-24 4:58 ` Stephen Rothwell
2008-10-24 4:58 ` Stephen Rothwell
2008-10-23 10:28 ` Hendrik Brueckner
2008-10-23 10:28 ` Hendrik Brueckner
2008-11-24 5:13 Stephen Rothwell
2008-11-24 9:59 ` Alan Cox
2009-04-20 3:09 Stephen Rothwell
2009-07-06 3:26 Stephen Rothwell
2009-07-14 4:10 Stephen Rothwell
2009-07-16 5:04 Stephen Rothwell
2009-07-17 3:12 Stephen Rothwell
2009-07-24 5:54 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=20080701152704.GB3973@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.