From: Oleksij Rempel <linux@rempel-privat.de>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "Proffit, Jerome" <jproffit@qca.qualcomm.com>,
ath9k-devel <ath9k-devel@qca.qualcomm.com>,
"Biard, David" <dbiard@qca.qualcomm.com>,
ath9k_htc_fw <ath9k_htc_fw@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: ath9k_htc: Target is unresponsive
Date: Fri, 15 Nov 2013 17:04:09 +0100 [thread overview]
Message-ID: <528645F9.9030708@rempel-privat.de> (raw)
In-Reply-To: <CAB=NE6U50eTLcUugBBBKz3fxa8yYcm+LCqgAtARzEnLpYqWg1g@mail.gmail.com>
Am 15.11.2013 16:33, schrieb Luis R. Rodriguez:
> On Fri, Nov 15, 2013 at 3:36 PM, Oleksij Rempel <linux@rempel-privat.de> wrote:
>> Am 15.11.2013 15:29, schrieb Luis R. Rodriguez:
>>> On Fri, Nov 15, 2013 at 3:18 PM, Oleksij Rempel <linux@rempel-privat.de> wrote:
>>>> I do not know which backport include patch for usb interrupt transfer.
>>>
>>> Which patch are you referring to? The backports project releases match
>>> the Linux kernel releases, so the backports-3.12 release is based on
>>> linux v3.12, we can check what kernel the patch you are describing got
>>> merged into Linux by doing:
>>>
>>> git describe --contains gitsum
>>
>> i mean:
>>
>> commit 2f5e3ecfc155449987d64028ff6b73f29cd1ef8b
>> Author: Oleksij Rempel <linux@rempel-privat.de>
>> Date: Tue Aug 13 09:29:34 2013 +0200
>>
>> ath9k_htc: do not use bulk on EP3 and EP4
>
> OK that is upstream commit ID 2b721118b7
>
> mcgrof@frijol ~/linux-stable (git::master)$ git describe --contains
> 2b721118b7821107757eb1d37af4b60e877b27e7
> v3.12-rc1~132^2~84^2^2~88
>
> This means that patch got merged into v3.12-rc1 which means the
> backports release based on v3.12 will have it.
>
>> If it is already included, then try to revert.
>
> What do you mean? Are you saying to try to revert that patch in case
> v3.12 backports release causes issues with the card?
yes
> It seems the user
> of this card had issues with the v3.10 release of backports which
> would not have this patch merged.
Ok. Thank you.
--
Regards,
Oleksij
next prev parent reply other threads:[~2013-11-15 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <39E4555519E9C54593B1BE31E24CB79A39B12884@nasanexd02a.na.qualcomm.com>
2013-11-15 13:47 ` ath9k_htc: Target is unresponsive Luis R. Rodriguez
2013-11-15 14:18 ` Oleksij Rempel
2013-11-15 14:29 ` Luis R. Rodriguez
2013-11-15 14:36 ` Oleksij Rempel
2013-11-15 15:33 ` Luis R. Rodriguez
2013-11-15 16:04 ` Oleksij Rempel [this message]
2013-11-15 16:07 ` Luis R. Rodriguez
2013-11-15 16:24 ` Oleksij Rempel
2013-05-15 13:42 Ignacy Gawedzki
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=528645F9.9030708@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=ath9k_htc_fw@lists.infradead.org \
--cc=dbiard@qca.qualcomm.com \
--cc=jproffit@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.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