From: David Miller <davem@davemloft.net>
To: haiyangz@microsoft.com
Cc: olaf@aepfle.de, netdev@vger.kernel.org, jasowang@redhat.com,
driverdev-devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next,v2] Add support for netvsc build without CONFIG_SYSFS flag
Date: Thu, 08 May 2014 16:44:58 -0400 (EDT) [thread overview]
Message-ID: <20140508.164458.157597820665207475.davem@davemloft.net> (raw)
In-Reply-To: <1399581693-25050-1-git-send-email-haiyangz@microsoft.com>
From: Haiyang Zhang <haiyangz@microsoft.com>
Date: Thu, 8 May 2014 13:41:33 -0700
> +static inline void netvsc_record_rx_queue(struct sk_buff *skb,
> + struct hv_netvsc_packet *packet,
> + struct net_device *ndev)
> +{
> +#ifdef CONFIG_SYSFS
> + skb_record_rx_queue(skb, packet->channel->
> + offermsg.offer.sub_channel_index %
> + ndev->real_num_rx_queues);
> +#endif
> +}
This is still fantastically gross, what is so unique about your
driver that it needs hacks like this? No other driver to my
knowledge does.
Figure out what it is that makes your driver so unique, and
try to make it conform to how other drivers handle these
features without SYSFS ifdef'ery instead.
I'm not applying this patch, sorry.
Thanks.
next prev parent reply other threads:[~2014-05-08 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 20:41 [PATCH net-next, v2] Add support for netvsc build without CONFIG_SYSFS flag Haiyang Zhang
2014-05-08 20:03 ` Greg KH
2014-05-08 20:41 ` Haiyang Zhang
2014-05-08 20:44 ` David Miller [this message]
2014-05-08 20:50 ` [PATCH net-next,v2] " Haiyang Zhang
2014-05-11 13:07 ` Ben Hutchings
2014-05-11 22:35 ` Haiyang Zhang
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=20140508.164458.157597820665207475.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
/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