Julian Calaby <[email protected]> writes: > Hi Jes, > > On Tue, Mar 1, 2016 at 9:05 AM, <[email protected]> wrote: >> From: Jes Sorensen <[email protected]> >> >> Having a version for the newer chips without calling it doesn't do >> much good..... >> >> Signed-off-by: Jes Sorensen <[email protected]> > > Should this be squashed into the patch that introduces the new op?
I can start rewriting history, but all that comes out of that is having to fight patch conflicts rebasing things. If there was an actual functional reason for it, sure, but in this case there isn't. Jes > >> --- >> drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c >> b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c >> index ecd0f59..566eeb5 100644 >> --- a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c >> +++ b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c >> @@ -7348,7 +7348,7 @@ static int rtl8xxxu_config(struct ieee80211_hw *hw, >> u32 changed) >> >> rtl8723a_set_tx_power(priv, channel, ht40); >> >> - rtl8723au_config_channel(hw); >> + priv->fops->config_channel(hw); >> } >> >> exit: > > Thanks, -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
