From: David Miller <davem@davemloft.net>
To: kvalo@codeaurora.org
Cc: hslester96@gmail.com, mlindner@marvell.com,
stephen@networkplumber.org, jirislaby@gmail.com,
mickflemm@gmail.com, mcgrof@kernel.org, sgruszka@redhat.com,
ath9k-devel@qca.qualcomm.com, merez@codeaurora.org,
johannes.berg@intel.com, emmanuel.grumbach@intel.com,
luciano.coelho@intel.com, amitkarwar@gmail.com,
nishants@marvell.com, gbhat@marvell.com, huxinming820@gmail.com,
imitsyanko@quantenna.com, avinashp@quantenna.com,
smatyukevich@quantenna.com, pkshih@realtek.com,
linuxwifi@intel.com, linux-net-drivers@solarflare.com,
ecree@solarflare.com, mhabets@solarflare.com,
netdev@vger.kernel.org, wil6210@qti.qualcomm.com,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 00/10] Use dev_get_drvdata where possible
Date: Wed, 24 Jul 2019 11:42:52 -0700 (PDT) [thread overview]
Message-ID: <20190724.114252.458305207498876259.davem@davemloft.net> (raw)
In-Reply-To: <87zhl3zlu1.fsf@kamboji.qca.qualcomm.com>
From: Kalle Valo <kvalo@codeaurora.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.
next prev parent reply other threads:[~2019-07-24 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 11:25 [PATCH net-next 00/10] Use dev_get_drvdata where possible Chuhong Yuan
2019-07-24 11:57 ` Kalle Valo
2019-07-24 18:42 ` David Miller [this message]
2019-07-24 18:45 ` David Miller
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=20190724.114252.458305207498876259.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amitkarwar@gmail.com \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=avinashp@quantenna.com \
--cc=ecree@solarflare.com \
--cc=emmanuel.grumbach@intel.com \
--cc=gbhat@marvell.com \
--cc=hslester96@gmail.com \
--cc=huxinming820@gmail.com \
--cc=imitsyanko@quantenna.com \
--cc=jirislaby@gmail.com \
--cc=johannes.berg@intel.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@solarflare.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luciano.coelho@intel.com \
--cc=mcgrof@kernel.org \
--cc=merez@codeaurora.org \
--cc=mhabets@solarflare.com \
--cc=mickflemm@gmail.com \
--cc=mlindner@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=nishants@marvell.com \
--cc=pkshih@realtek.com \
--cc=sgruszka@redhat.com \
--cc=smatyukevich@quantenna.com \
--cc=stephen@networkplumber.org \
--cc=wil6210@qti.qualcomm.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