All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Enrico Tagliavini <enrico.tagliavini@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Michal Kazior <michal.kazior@tieto.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2
Date: Wed, 29 Jul 2015 12:30:07 +0300	[thread overview]
Message-ID: <874mkn71ls.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAMQd7mY+upL+t9q0yJ0uL_jw_STEKL+hhe1PF_D5yPwfTkcgZg@mail.gmail.com> (Enrico Tagliavini's message of "Wed, 29 Jul 2015 11:02:40 +0200")

Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:

> Yeah that's what I meant. My idea was to first bisect only the ath10k
> directory, so restricting the bisect on the commits touching stuff
> there. I guess if the issue is more broad it will come up somewhere
> else as well, so this is a good starting point, I hope. Thank you for
> pointing it out though, this will actually be the first time I do a
> proper bisect.

And remember to always to mention if you have restricted the bisect
somehow, that's important information. And better if you provide 'git
bisect log' output as well.

> Also do you want me to bisect Kalle's sources or Linus' master? By
> what Michał said I guess Kalle's but I ask to be sure.
>
> Also to be clear: I'm using Linus' sources at the moment, as provided
> by Fedora rawhide.
>
> For me it's the same, so let me know what you prefer and is more
> useful to solve this issue.

Good that you brought this up. As ath.git master branch gets rebased
every rc1 release you really cannot use that for bisect. Either you
should use ath.git ath-next branch or Linus' tree. To be on the safe
side I always recommend to use Linus' tree if at all possible.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Enrico Tagliavini <enrico.tagliavini@gmail.com>
Cc: Michal Kazior <michal.kazior@tieto.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2
Date: Wed, 29 Jul 2015 12:30:07 +0300	[thread overview]
Message-ID: <874mkn71ls.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAMQd7mY+upL+t9q0yJ0uL_jw_STEKL+hhe1PF_D5yPwfTkcgZg@mail.gmail.com> (Enrico Tagliavini's message of "Wed, 29 Jul 2015 11:02:40 +0200")

Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:

> Yeah that's what I meant. My idea was to first bisect only the ath10k
> directory, so restricting the bisect on the commits touching stuff
> there. I guess if the issue is more broad it will come up somewhere
> else as well, so this is a good starting point, I hope. Thank you for
> pointing it out though, this will actually be the first time I do a
> proper bisect.

And remember to always to mention if you have restricted the bisect
somehow, that's important information. And better if you provide 'git
bisect log' output as well.

> Also do you want me to bisect Kalle's sources or Linus' master? By
> what Michał said I guess Kalle's but I ask to be sure.
>
> Also to be clear: I'm using Linus' sources at the moment, as provided
> by Fedora rawhide.
>
> For me it's the same, so let me know what you prefer and is more
> useful to solve this issue.

Good that you brought this up. As ath.git master branch gets rebased
every rc1 release you really cannot use that for bisect. Either you
should use ath.git ath-next branch or Linus' tree. To be on the safe
side I always recommend to use Linus' tree if at all possible.

-- 
Kalle Valo

  reply	other threads:[~2015-07-29  9:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 20:08 QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2 Enrico Tagliavini
2015-07-27 20:08 ` Enrico Tagliavini
2015-07-28  4:31 ` Michal Kazior
2015-07-28  4:31   ` Michal Kazior
2015-07-28 11:00   ` Enrico Tagliavini
2015-07-28 11:00     ` Enrico Tagliavini
2015-07-28 11:26     ` Michal Kazior
2015-07-28 11:26       ` Michal Kazior
2015-07-28 14:57       ` Enrico Tagliavini
2015-07-28 14:57         ` Enrico Tagliavini
2015-07-28 15:12         ` Alexandre Maloteaux
2015-07-28 15:50           ` Enrico Tagliavini
2015-07-29  5:25           ` Michal Kazior
2015-07-29  5:28         ` Michal Kazior
2015-07-29  5:28           ` Michal Kazior
2015-07-29  6:54           ` Kalle Valo
2015-07-29  6:54             ` Kalle Valo
2015-07-29  9:02             ` Enrico Tagliavini
2015-07-29  9:02               ` Enrico Tagliavini
2015-07-29  9:30               ` Kalle Valo [this message]
2015-07-29  9:30                 ` Kalle Valo
2015-07-29 14:22                 ` Enrico Tagliavini
2015-07-29 14:22                   ` Enrico Tagliavini
2015-08-01 12:30                   ` Enrico Tagliavini
2015-08-01 12:30                     ` Enrico Tagliavini
2015-08-05 17:52                     ` Enrico Tagliavini
2015-08-05 17:52                       ` Enrico Tagliavini
2015-09-08  8:17                       ` Enrico Tagliavini
2015-09-08  8:17                         ` Enrico Tagliavini
2015-10-20 11:39                         ` Enrico Tagliavini
2015-10-20 11:39                           ` Enrico Tagliavini

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=874mkn71ls.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=enrico.tagliavini@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.kazior@tieto.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.