[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190724.114252.458305207498876259.davem@davemloft.net>
Date: Wed, 24 Jul 2019 11:42:52 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: kvalo@...eaurora.org
Cc: hslester96@...il.com, mlindner@...vell.com,
stephen@...workplumber.org, jirislaby@...il.com,
mickflemm@...il.com, mcgrof@...nel.org, sgruszka@...hat.com,
ath9k-devel@....qualcomm.com, merez@...eaurora.org,
johannes.berg@...el.com, emmanuel.grumbach@...el.com,
luciano.coelho@...el.com, amitkarwar@...il.com,
nishants@...vell.com, gbhat@...vell.com, huxinming820@...il.com,
imitsyanko@...ntenna.com, avinashp@...ntenna.com,
smatyukevich@...ntenna.com, pkshih@...ltek.com,
linuxwifi@...el.com, linux-net-drivers@...arflare.com,
ecree@...arflare.com, mhabets@...arflare.com,
netdev@...r.kernel.org, wil6210@....qualcomm.com,
linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 00/10] Use dev_get_drvdata where possible
From: Kalle Valo <kvalo@...eaurora.org>
Date: Wed, 24 Jul 2019 14:57:42 +0300
> Do note that wireless patches go to wireless-drivers-next, not net-next.
> But I assume Dave will ignore patches 5-10 and I can take them.
Yes, that is what I plan to do.
Powered by blists - more mailing lists