From: David Miller <davem@davemloft.net>
To: ying.xue@windriver.com
Cc: vfalico@redhat.com, john.r.fastabend@intel.com,
stephen@networkplumber.org, antonio@meshcoding.com,
dmitry.tarnyagin@lockless.no, socketcan@hartkopp.net,
johannes@sipsolutions.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 00/10] use appropriate APIs to get interfaces
Date: Tue, 14 Jan 2014 18:53:19 -0800 (PST) [thread overview]
Message-ID: <20140114.185319.701097353751396242.davem@davemloft.net> (raw)
In-Reply-To: <1389752625-23189-1-git-send-email-ying.xue@windriver.com>
From: Ying Xue <ying.xue@windriver.com>
Date: Wed, 15 Jan 2014 10:23:35 +0800
> Under rtnl_lock protection, we should use __dev_get_name/index()
> rather than dev_get_name()/index() to find interface handlers
> because the former interfaces can help us avoid to change interface
> reference counter.
>
> v2 changes:
> - Change return value of nl80211_set_wiphy() to 0 in patch #10
> by johannes's suggestion.
> - Add 'Acked-by' into several patches which were acknowledged by
> corresponding maintainers.
This looks fine, series applied, thanks.
prev parent reply other threads:[~2014-01-15 2:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 2:23 [PATCH net-next v2 00/10] use appropriate APIs to get interfaces Ying Xue
2014-01-15 2:23 ` [PATCH net-next v2 01/10] Drivers: Staging: cxt1e1: use __dev_get_name instead of dev_get_name to find interfaces Ying Xue
2014-01-15 2:23 ` [PATCH net-next v2 02/10] bonding: use __dev_get_by_name instead of dev_get_by_name to find interface Ying Xue
2014-01-15 2:23 ` [PATCH net-next v2 03/10] eql: " Ying Xue
2014-01-15 2:23 ` [PATCH net-next v2 04/10] dcb: " Ying Xue
2014-01-15 2:23 ` [PATCH net-next v2 05/10] decnet: use __dev_get_by_index instead of dev_get_by_index " Ying Xue
2014-01-15 2:23 ` [PATCH net-next v2 06/10] vxlan: " Ying Xue
2014-01-15 2:23 ` [PATCH net-next v2 07/10] batman-adv: " Ying Xue
2014-01-15 2:23 ` [PATCH net-next v2 08/10] caif: " Ying Xue
2014-01-15 2:23 ` [PATCH net-next v2 09/10] can: use " Ying Xue
2014-01-15 2:23 ` [PATCH net-next v2 10/10] net: nl80211: " Ying Xue
2014-01-15 2:53 ` David Miller [this message]
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=20140114.185319.701097353751396242.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=antonio@meshcoding.com \
--cc=dmitry.tarnyagin@lockless.no \
--cc=johannes@sipsolutions.net \
--cc=john.r.fastabend@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=stephen@networkplumber.org \
--cc=vfalico@redhat.com \
--cc=ying.xue@windriver.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