All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Disconnect problem (DMA failed to stop in 10 ms)
Date: Tue, 18 Aug 2009 17:45:00 -0400	[thread overview]
Message-ID: <1250631900.7534.44.camel@mj> (raw)
In-Reply-To: <43e72e890908181424l770b3356ie990e9cadcb39877@mail.gmail.com>

On Tue, 2009-08-18 at 14:24 -0700, Luis R. Rodriguez wrote:

> > Anyway, why is it better for bisecting?
> 
> Because to help developers not have to do:
> 
> git branch -m poo
> git checkout -b master origin/master
> # Then apply patches manually
> 
> Instead of the better rebasing:
> 
> git branch -m save-my-stuff
> git checkout -b master origin/master
> git checkout save-my-stuff
> git rebase master

I use STGit, so perhaps I miss all that fun.  I have never had any
trouble tracking wireless-testing while keeping my patches.

> john reverts his patches on wireless-testing before rebasing to Linus'
> tree. There may be some other added benefit other than helping us
> rebase cleanly, not sure. But I do remember before that I never was
> able to rebase my patches, and now rebasing works quite nicely.

You mean it's better to track wireless-next-2.6 for those of us trying
to stay on top of the wireless development?  I must have missed the
memo.  Indeed, wireless-next-2.6 has a couple of commits that
wireless-testing doesn't have yet.

I agree that having to bisect through reverts is not fun, and it takes
one or two extra iterations.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2009-08-18 21:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13  1:16 [ath9k-devel] Disconnect problem (DMA failed to stop in 10 ms) Michael Gruber
2009-08-13  3:45 ` Pavel Roskin
2009-08-13  3:54   ` Sujith
2009-08-13  4:22     ` Pavel Roskin
2009-08-13  5:21       ` Sujith
2009-08-13  5:40         ` Pavel Roskin
2009-08-18 18:16           ` Kunal Gangakhedkar
2009-08-18 21:04             ` Pavel Roskin
2009-08-18 21:07               ` Luis R. Rodriguez
2009-08-18 21:15                 ` Pavel Roskin
2009-08-18 21:24                   ` Luis R. Rodriguez
2009-08-18 21:45                     ` Pavel Roskin [this message]
2009-08-18 21:57                       ` Luis R. Rodriguez
2009-08-19 17:58                         ` John W. Linville
2009-08-19 18:34                           ` [ath9k-devel] bisecting with wireless-testing Luis R. Rodriguez
2009-08-19 18:34                             ` Luis R. Rodriguez
2009-08-19 18:44                             ` [ath9k-devel] " John W. Linville
2009-08-19 18:44                               ` John W. Linville
2009-08-20  7:13               ` [ath9k-devel] Disconnect problem (DMA failed to stop in 10 ms) Kunal Gangakhedkar
2009-08-19  3:51             ` Sujith
2009-08-20  7:14               ` Kunal Gangakhedkar
2009-08-24 20:58               ` Kunal Gangakhedkar
2009-09-11 15:42                 ` Kunal Gangakhedkar
2009-08-13  7:59         ` Kunal Gangakhedkar
     [not found] <1253068000.2813.11.camel@localhost.localdomain>
2009-09-16  7:35 ` Kunal Gangakhedkar
2009-09-16  7:35   ` Kunal Gangakhedkar

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=1250631900.7534.44.camel@mj \
    --to=proski@gnu.org \
    --cc=ath9k-devel@lists.ath9k.org \
    /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.