Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755940AbaGQJRW (ORCPT ); Thu, 17 Jul 2014 05:17:22 -0400 Received: from mail-yh0-f49.google.com ([209.85.213.49]:64138 "EHLO mail-yh0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754137AbaGQJRT (ORCPT ); Thu, 17 Jul 2014 05:17:19 -0400 MIME-Version: 1.0 X-Originating-IP: [84.208.72.173] In-Reply-To: <1405587855.20120.0.camel@jlt4.sipsolutions.net> References: <1405584370-30054-1-git-send-email-teg@jklm.no> <1405584370-30054-3-git-send-email-teg@jklm.no> <1405587855.20120.0.camel@jlt4.sipsolutions.net> From: Tom Gundersen Date: Thu, 17 Jul 2014 11:16:56 +0200 Message-ID: Subject: Re: [PATCH net-next v9 2/9] net: nl80211 - make rdev_add_virtual_intf take name_assign_type To: Johannes Berg Cc: netdev , David Miller , LKML , John Linville Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 17, 2014 at 11:04 AM, Johannes Berg wrote: > On Thu, 2014-07-17 at 10:06 +0200, Tom Gundersen wrote: >> Pass the value down and set it at the same place the name itself is set. > > Huh? What's this? Can you explain why? Sure, sorry the context got lost. We want to expose the origin of ifnames so that udev can better decide whether or not to rename them. In particular, this patch will allow udev to tell that it should no longer rename Wifi-P2P devices, which is currently a problem. A general overview is in the patch introducing the interface: . >> static struct wireless_dev *ath6kl_cfg80211_add_iface(struct wiphy *wiphy, >> const char *name, >> + unsigned char name_assign_type, > > unsigned char for an enum is really odd. Hm, this was based on the addr_assign_type attribute, which also is an unsigned char (and serves a very similar purpose). Out of interest, what would you have preferred (and why)? Cheers, Tom -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/