From: Jesper Nilsson <Jesper.Nilsson@axis.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Hinko Ko??evar <hinko.kocevar@cetrtapot.si>,
Mikael Starvik <mikael.starvik@axis.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dev-etrax <dev-etrax@axis.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH 2.6.26-rc5 0/2] cris: compile fixes for 2.6.26-rc5
Date: Tue, 10 Jun 2008 11:49:37 +0200 [thread overview]
Message-ID: <20080610094937.GC4081@axis.com> (raw)
In-Reply-To: <20080606183222.GE2201@cs181133002.pp.htv.fi>
On Fri, Jun 06, 2008 at 08:32:22PM +0200, Adrian Bunk wrote:
> On Fri, Jun 06, 2008 at 01:36:26PM +0200, Hinko Ko??evar wrote:
> > Hi,
> >
> > Current status of cris architecture is that current GIT tree at 2.6.26-rc5 does
> > not even compile.
> >...
>
> @Mikael, Jesper:
>
> BTW:
> What happened with the stuff you have?
> It seems you missed to merge for 2.6.26?
Yeah, unfortunately I got swamped just as the 2.6.26 merge window opened up.
I'll push them out for 2.6.27.
> Can you try to not miss the merge window for 2.6.27, and also publish
> your queued patches in a way that they might get into the -next tree
> (Stephen Cc'ed for possibly discussing details)?
Have I understood correctly that a tree exported for -next can be rebased
without causing any problems? I've hesitated a bit to create a -next tree
to avoid problems with later merges.
> > Best regards,
> > Hinko
>
> TIA
> Adrian
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@axis.com
next prev parent reply other threads:[~2008-06-10 9:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 11:36 [PATCH 2.6.26-rc5 0/2] cris: compile fixes for 2.6.26-rc5 Hinko Kočevar
2008-06-06 11:37 ` [PATCH 2.6.26-rc5 1/2] " Hinko Kočevar
2008-06-06 11:41 ` Alan Cox
2008-06-06 12:12 ` Hinko Koc(evar
2008-06-06 15:05 ` Alan Cox
2008-06-06 11:38 ` [PATCH 2.6.26-rc5 2/2] " Hinko Kočevar
2008-06-06 18:32 ` [PATCH 2.6.26-rc5 0/2] " Adrian Bunk
2008-06-10 9:49 ` Jesper Nilsson [this message]
2008-06-10 10:15 ` Stephen Rothwell
2008-07-01 14:08 ` [PATCH linux-next 1/1] cris: look for linker scripts in srctree not in objtree Hinko Kocevar
2008-07-01 16:02 ` Jesper Nilsson
2008-07-01 19:29 ` Sam Ravnborg
2008-07-02 7:13 ` Hinko Kocevar
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=20080610094937.GC4081@axis.com \
--to=jesper.nilsson@axis.com \
--cc=bunk@kernel.org \
--cc=dev-etrax@axis.com \
--cc=hinko.kocevar@cetrtapot.si \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael.starvik@axis.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox