All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, linux-zigbee-devel@lists.sourceforge.net
Subject: Re: 6lowpan: lockless tx queue of routing netlink device
Date: Mon, 10 Feb 2014 20:31:44 +0100	[thread overview]
Message-ID: <20140210193142.GA17018@omega> (raw)
In-Reply-To: <1392060372.6615.41.camel@edumazet-glaptop2.roam.corp.google.com>

On Mon, Feb 10, 2014 at 11:26:12AM -0800, Eric Dumazet wrote:
> On Mon, 2014-02-10 at 19:21 +0100, Alexander Aring wrote:
> 
> > no problem. Maybe you can try to give me some explanation what you did
> > there?
> > 
> > I see you make a lockdep_set_class for each tx queue and assign the 
> > lowpan_netdev_xmit_lock_key. So why it's better to make a own
> > "lock_key".
> 
> This will be explained in the patch I'll cook.
> 
Okay, then you can add a

Tested-by: Alexander Aring <alex.aring@gmail.com>

Thanks!

- Alex

  reply	other threads:[~2014-02-10 19:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-09 10:20 6lowpan: lockless tx queue of routing netlink device Alexander Aring
2014-02-09 12:41 ` Eric Dumazet
     [not found]   ` <1391949707.10160.130.camel-XN9IlZ5yJG9HTL0Zs8A6p/gx64E7kk8eUsxypvmhUTTZJqsBc5GL+g@public.gmane.org>
2014-02-10 17:33     ` Alexander Aring
2014-02-10 18:16       ` Eric Dumazet
2014-02-10 18:21         ` Alexander Aring
2014-02-10 19:26           ` Eric Dumazet
2014-02-10 19:31             ` Alexander Aring [this message]
2014-02-10 19:42   ` [PATCH] 6lowpan: fix lockdep splats Eric Dumazet
2014-02-11  1:51     ` David Miller

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=20140210193142.GA17018@omega \
    --to=alex.aring@gmail.com \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-zigbee-devel@lists.sourceforge.net \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.