From: Adrian Bunk <bunk@kernel.org>
To: "Hinko Kočevar" <hinko.kocevar@cetrtapot.si>,
starvik@axis.com, jesper.nilsson@axis.com
Cc: linux-kernel@vger.kernel.org, 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: Fri, 6 Jun 2008 21:32:22 +0300 [thread overview]
Message-ID: <20080606183222.GE2201@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <4849213A.4080001@cetrtapot.si>
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?
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)?
> Best regards,
> Hinko
TIA
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-06-06 18:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 11:36 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 ` Adrian Bunk [this message]
2008-06-10 9:49 ` [PATCH 2.6.26-rc5 0/2] " Jesper Nilsson
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=20080606183222.GE2201@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=dev-etrax@axis.com \
--cc=hinko.kocevar@cetrtapot.si \
--cc=jesper.nilsson@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=starvik@axis.com \
/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
all inboxes | Powered by JetHome®