[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140508.164458.157597820665207475.davem@davemloft.net>
Date: Thu, 08 May 2014 16:44:58 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: haiyangz@...rosoft.com
Cc: netdev@...r.kernel.org, kys@...rosoft.com, olaf@...fle.de,
jasowang@...hat.com, linux-kernel@...r.kernel.org,
driverdev-devel@...uxdriverproject.org
Subject: Re: [PATCH net-next,v2] Add support for netvsc build without
CONFIG_SYSFS flag
From: Haiyang Zhang <haiyangz@...rosoft.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists