On Wed, Feb 24, 2010 at 7:33 AM, Helmut Schaa
<[email protected]> wrote:
> ath9k_htc does not build against current wireless-testing due to recent
> changes in mac80211 ("mac80211: remove struct ieee80211_if_init_conf").
>
> Fix this by updating the add_interface and remove_interface callbacks to
> use ieee80211_vif instead of ieee80211_if_init_conf.
>
> Signed-off-by: Helmut Schaa <[email protected]>
Thanks! Applied and pushed out. I should note, since no one else has,
that ath9k_htc has gotten a huge face lift by now. Unfortunately the
entire new revamp was done through an internal private tree but from
what I gather submission upstream should happen soon.
Luis
Helmut Schaa wrote:
> Am Mittwoch 24 Februar 2010 schrieb Luis R. Rodriguez:
> > Thanks! Applied and pushed out. I should note, since no one else has,
> > that ath9k_htc has gotten a huge face lift by now. Unfortunately the
> > entire new revamp was done through an internal private tree but from
> > what I gather submission upstream should happen soon.
>
> Does it make much sense then to hack on the driver right now?
> Should linux-wireless be CC'ed as well for ath9k_htc patches?
We would be making a submission soon, as soon as a few
internal tests are run.
I would think that holding off work on the public ath9k_htc tree would be good.
Patches are always welcome for the driver after the submission. :)
Sujith
Am Mittwoch 24 Februar 2010 schrieb Luis R. Rodriguez:
> Thanks! Applied and pushed out. I should note, since no one else has,
> that ath9k_htc has gotten a huge face lift by now. Unfortunately the
> entire new revamp was done through an internal private tree but from
> what I gather submission upstream should happen soon.
Does it make much sense then to hack on the driver right now?
Should linux-wireless be CC'ed as well for ath9k_htc patches?
Thanks,
Helmut