Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Varka Bhadram <varkabhadram@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org, Varka Bhadram <varkab@cdac.in>
Subject: Re: [PATCH bluetooth-next] cfg802154: pass name_assign_type to rdev_add_virtual_intf()
Date: Wed, 29 Apr 2015 08:52:44 +0530	[thread overview]
Message-ID: <55404E84.6020805@gmail.com> (raw)
In-Reply-To: <20150428142932.GA758@omega>

On 04/28/2015 07:59 PM, Alexander Aring wrote:
> On Tue, Apr 28, 2015 at 02:18:10PM +0530, Varka Bhadram wrote:
>> This code is based on commit 6bab2e19c5ffd
>> ("cfg80211: pass name_assign_type to rdev_add_virtual_intf()")
>>
>> This will expose in sysfs whether the ifname of a IEEE-802.15.4
>> device is set by userspace or generated by the kernel.
>> We are using two types of name_assign_types
>>  o NET_NAME_ENUM: Default interface name provided by kernel
>>  o NET_NAME_USER: Interface name provided by user.
>>
> grml, this patch is fine but it doesn't apply when we have the
> ("ieee802154: Add trace events for rdev->ops") commit applied before. I
> reanimate the linux-wpan-next master branch now.
>
> Can you please rebase your patch on this [0]?
>
> - Alex
>
> [0] https://github.com/linux-wpan/linux-wpan-next/commits/master

Sure. Will do.

-- 
Varka Bhadram


      reply	other threads:[~2015-04-29  3:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28  8:48 [PATCH bluetooth-next] cfg802154: pass name_assign_type to rdev_add_virtual_intf() Varka Bhadram
2015-04-28 10:48 ` Alexander Aring
2015-04-28 14:29 ` Alexander Aring
2015-04-29  3:22   ` Varka Bhadram [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=55404E84.6020805@gmail.com \
    --to=varkabhadram@gmail.com \
    --cc=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=varkab@cdac.in \
    /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