All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hin-Tak Leung <htl10@users.sourceforge.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@winlab.rutgers.edu>,
	"compat-masters@lists.madwifi.org"
	<compat-masters@lists.madwifi.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	dwmw2@infradead.org, dcbw@redhat.com, linville@tuxdriver.com,
	tim.gardner@canonical.com
Subject: Re: a couple of small bugs in compat-wireless -- libertas
Date: Wed, 12 Nov 2008 01:40:22 +0000 (GMT)	[thread overview]
Message-ID: <33409.76636.qm@web23104.mail.ird.yahoo.com> (raw)
In-Reply-To: <43e72e890811111702x7b817c4bpdeed5acf39b2a5fd@mail.gmail.com>

--- On Wed, 12/11/08, Luis R. Rodriguez <mcgrof@gmail.com> wrote:

> From: Luis R. Rodriguez <mcgrof@gmail.com>
<snipped>
> > OK for your issue you can try this patch.
> 
> This patch should actually be useless to you as you
> probably are just
> downloading the tarball.. so just download the latest
> tarball, I just
> regenerated it with the patches applied.

Thanks for doing this - I actually do both: I have local git-clones of compat-wireless and and wireless-testing, which I use for checking out the "latest and greatest". However, to hunt down a regression which turned out to happen about 20 days ago, I had to roll back both of them and it was getting a bit painful to roll them back in sync, so I downloaded two whole months' worth of daily tarballs and bisected the "old fashion way" until I got within a day, then I read the tags off two daily snapshots and use the git-clone to spit out the 48 commits within that day. Some of the 48 are obviously irrelevant so it narrows it down to under 20 probables, and just a few obvious candidates. Then back to one of the snapshots and try out the obvious candidates; found the commit which breaks and verify that it breaks git-clone HEAD, etc. So it was going back and forth between the daily tarballs and the git-clones. 

Thanks for compat-wireless - it takes about 1/2 hour to build a snapshot (I just worked out how to edit the Makefile to skip some bits I
don't need, so it has gone quicker), but it is better than building a whole new kernel... and the best thing about it is that I don't have to reboot, just losing connectivity briefly (hopefully) to swap and try new snapshots.

Hin-Tak 


      

      reply	other threads:[~2008-11-12  1:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11  5:28 a couple of small bugs in compat-wireless Hin-Tak Leung
2008-11-11 23:12 ` Luis R. Rodriguez
2008-11-12  0:54   ` a couple of small bugs in compat-wireless -- libertas Luis R. Rodriguez
2008-11-12  1:02     ` Luis R. Rodriguez
2008-11-12  1:40       ` Hin-Tak Leung [this message]

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=33409.76636.qm@web23104.mail.ird.yahoo.com \
    --to=htl10@users.sourceforge.net \
    --cc=compat-masters@lists.madwifi.org \
    --cc=dcbw@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --cc=mcgrof@winlab.rutgers.edu \
    --cc=tim.gardner@canonical.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.