lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080610094937.GC4081@axis.com>
Date:	Tue, 10 Jun 2008 11:49:37 +0200
From:	Jesper Nilsson <Jesper.Nilsson@...s.com>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Hinko Ko??evar <hinko.kocevar@...rtapot.si>,
	Mikael Starvik <mikael.starvik@...s.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	dev-etrax <dev-etrax@...s.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH 2.6.26-rc5 0/2] cris: compile fixes for 2.6.26-rc5

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@...s.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ