From: Johannes Stezenbach <js@sig21.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Ivo Van Doorn <ivdoorn@gmail.com>
Subject: Re: Compat-wireless release for 2010-10-25 is baked
Date: Tue, 26 Oct 2010 20:41:23 +0200 [thread overview]
Message-ID: <20101026184123.GA1616@sig21.net> (raw)
In-Reply-To: <AANLkTimzUKj=C9PxGs1PkQy_KWu0PGKd1zv_m-ZpWaEm@mail.gmail.com>
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@sig21.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
next prev parent reply other threads:[~2010-10-26 18:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 19:03 Compat-wireless release for 2010-10-25 is baked Compat-wireless cronjob account
2010-10-26 12:35 ` Johannes Stezenbach
2010-10-26 15:59 ` Luis R. Rodriguez
2010-10-26 18:41 ` Johannes Stezenbach [this message]
2010-10-26 18:51 ` Luis R. Rodriguez
2010-10-26 19:48 ` Ivo Van Doorn
2010-10-26 20:40 ` Johannes Stezenbach
2010-10-26 20:52 ` Luis R. Rodriguez
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=20101026184123.GA1616@sig21.net \
--to=js@sig21.net \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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;
as well as URLs for NNTP newsgroup(s).