linux-kernel - Re: Compat-wireless release for 2010-10-25 is baked

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: <20101026184123.GA1616@sig21.net>
Date:	Tue, 26 Oct 2010 20:41:23 +0200
From:	Johannes Stezenbach <js@...21.net>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
Cc:	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
	Ivo Van Doorn <ivdoorn@...il.com>
Subject: Re: Compat-wireless release for 2010-10-25 is baked

On Tue, Oct 26, 2010 at 08:59:04AM -0700, Luis R. Rodriguez wrote:
> On Tue, Oct 26, 2010 at 5:35 AM, Johannes Stezenbach <js@...21.net> wrote:
> >
> > I wonder about the different tarballs in
> > http://wireless.kernel.org/download/compat-wireless-2.6/
> >
> > compat-wireless-2010-10-25.tar.bz2
> > compat-wireless-2010-10-25-p.tar.bz2
> > compat-wireless-2010-10-25-pc.tar.bz2
> >
> > Those -p and -pc postfixes are not explained in
> > http://wireless.kernel.org/en/users/Download
> 
> Right, sorry, I haven't updated the docs to add documentation for
> them. First please read:
> 
> http://marc.info/?l=linux-wireless&m=128716953726075&w=2
> 
> -s is for getting and applying pending-stable/ fixes
> -n is for applying the patches linux-next-cherry-picks directory
> -p is for applying the patches on the linux-next-pending directory
> -s is for applying the patches on the crap directory
  -c

> Hope this helps.

Definitively, thank you very much.  Meanwhile I also found
scripts/admin-update.sh in compat-wireless which seems to
generate the release tarballs.

It looks like, if I want to test the latest rt2x00 code, I could
clone git://git.kernel.org/pub/scm/linux/kernel/git/ivd/rt2x00.git,
checkout experimental, and then run admin-update.sh with
GIT_TREE=path/to/rt2x00-experimental.  Right?
Or (maybe better?), clone linux-next, merge rt2x00.git and use
the merged tree as GIT_TREE for admin-update.sh.

But according to
http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2010-October/002175.html
the compat-rt2x00 tarballs seem to be made manually?

Sorry for stupid questions, I want to get into rt2x00 development
but I need to target a stable 2.6.32 kernel and I'm trying to figure
out which git tree to base my work on.

Thanks,
Johannes
--
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/