From: Elias Oltmanns <eo@nebensachen.de>
To: "Nick Kossifidis" <mickflemm@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Jiri Slaby" <jirislaby@gmail.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath5k: Fix reset sequence for AR5212 in general and RF5111 in particular
Date: Wed, 29 Oct 2008 16:07:06 +0100 [thread overview]
Message-ID: <87wsfrqw2t.fsf@denkblock.local> (raw)
In-Reply-To: <40f31dec0810290749u2c065d17g5788eb22cf508142@mail.gmail.com> (Nick Kossifidis's message of "Wed, 29 Oct 2008 16:49:29 +0200")
"Nick Kossifidis" <mickflemm@gmail.com> wrote:
> 2008/10/29 Elias Oltmanns <eo@nebensachen.de>:
>>
>
>> Right, so here is another attempt. Unfortunately, in 2.6.27 no constants
>> have been defined for the phy revisions, nor the 0xa228 register and the
>> bit masks involved in resetting this register. Perhaps we should consult
>> the stable team on this matter because the minimal approach, as
>> presented below, certainly lacks even the smallest degree of readability
>> even though we actually know reasonably well what we are doing here. The
>> changelog, by the way, will be adapted to quote your changeset fixing
>> this in mainline once it has been committed. What do you think?
>>
>
> Patch looks OK, thanks a lot ;-)
>
> John can we get this get in stable until i update reset.c on wireless-testing ?
> Would it be possible later to update mainline from wireless-testing ?
Reading Documentation/stable_kernel_rules.txt, I very much doubt that
this patch will go in unless we can at least point out something
equivalent in mainline. So, we'll have to wait until your changes to
reset.c have reached mainline, I'm afraid.
Regards,
Elias
next prev parent reply other threads:[~2008-10-29 15:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87prlr9mna.fsf@denkblock.local>
2008-10-25 23:21 ` [PATCH] ath5k: Fix reset sequence for AR5212 in general and RF5111 in particular Nick Kossifidis
2008-10-26 17:52 ` Elias Oltmanns
2008-10-26 18:32 ` Nick Kossifidis
2008-10-26 20:47 ` Elias Oltmanns
2008-10-26 22:33 ` Nick Kossifidis
2008-10-26 22:52 ` Elias Oltmanns
2008-10-27 20:31 ` Nick Kossifidis
2008-10-29 13:25 ` Elias Oltmanns
2008-10-29 14:49 ` Nick Kossifidis
2008-10-29 15:07 ` Elias Oltmanns [this message]
2008-10-29 15:28 ` Bob Copeland
2008-10-29 17:51 ` Nick Kossifidis
2008-10-29 23:25 ` Elias Oltmanns
2008-10-29 23:34 ` John W. Linville
2008-10-29 23:56 ` Elias Oltmanns
2008-10-30 0:04 ` Elias Oltmanns
2008-10-27 18:36 ` Nils
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=87wsfrqw2t.fsf@denkblock.local \
--to=eo@nebensachen.de \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=mickflemm@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).