From: Larry Finger <Larry.Finger@lwfinger.net>
To: lolilolicon <lolilolicon@gmail.com>, ath9k-devel@qca.qualcomm.com
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
John Linville <linville@tuxdriver.com>
Subject: Re: Bug: USB wifi card TL-WN722N (AR9271, ath9k_htc) fails to get DHCP lease
Date: Sun, 29 Jun 2014 12:08:07 -0500 [thread overview]
Message-ID: <53B047F7.2000204@lwfinger.net> (raw)
In-Reply-To: <CAMtVo_PAkxCkxO7ETV6r=Xg75LLRt0GHi8GdqhT4tXKZSpmOvQ@mail.gmail.com>
On 06/29/2014 04:32 AM, lolilolicon wrote:
> On Sun, Jun 29, 2014 at 8:37 AM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
>>
>> Something went wrong in your bisection. Commit 88daf80 is a merge commit and
>> is unlikely to be the bad one. You might try a checkout of b080e04 and try
>> it to see if it is bad or good. That is the first non-merge commit before
>> 88daf80.
>>
>> Larry
>>
>
> I have no clue how you identified b080e04, but I tested it and it is good.
> I'm not good at git so please bear with me. What I know is 88daf80 is
> bad, and both its two parents 010d3c3 and 35582ad are good: does that
> not mean 88daf80 is the first bad commit?
>
> % git bisect start 88daf80 010d3c3 35582ad
> 88daf80dcca19ff995cc263592426f734a9702f3 is the first bad commit
>
> What am I getting wrong?
I am not an expert in git, but I think you are being too restrictive with that
command. If you do "git bisect start 88daf80 010d3c3", there are ath9k patches
in the code left to test. With the other option "git bisect start 88daf80
35582ad", git visualize does not show any ath9k changes.
Larry
next prev parent reply other threads:[~2014-06-29 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 21:17 Bug: USB wifi card TL-WN722N (AR9271, ath9k_htc) fails to get DHCP lease lolilolicon
2014-06-29 0:37 ` Larry Finger
2014-06-29 9:32 ` lolilolicon
2014-06-29 17:08 ` Larry Finger [this message]
2014-06-29 21:08 ` lolilolicon
2014-06-30 14:20 ` John W. Linville
2014-06-30 17:24 ` [ath9k-devel] " Oleksij Rempel
2014-07-01 4:41 ` Nathan Schulte
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=53B047F7.2000204@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=ath9k-devel@lists.ath9k.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lolilolicon@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).