All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Martin Townsend <martin.townsend@xsilon.com>
Cc: linux-zigbee-devel@lists.sourceforge.net,
	linux-bluetooth@vger.kernel.org, linux-wpan@vger.kernel.org,
	Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [PATCH bluetooth-next] 6lowpan: Remove ununsed dev parameter from skb_delivery_cb callback.
Date: Fri, 1 Aug 2014 11:41:46 +0200	[thread overview]
Message-ID: <20140801094144.GA11159@omega> (raw)
In-Reply-To: <53DB5A53.5000004@xsilon.com>

Hi Martin,

On Fri, Aug 01, 2014 at 10:13:55AM +0100, Martin Townsend wrote:
> This parameter is never used by any function implementing this callback.
> ---
>  include/net/6lowpan.h         | 2 +-
>  net/6lowpan/iphc.c            | 2 +-
>  net/bluetooth/6lowpan.c       | 4 ++--
>  net/ieee802154/6lowpan_rtnl.c | 5 ++---
>  4 files changed, 6 insertions(+), 7 deletions(-)
> 

I don't test it yet, but you need to add a Signed-off-by: ...

You can create this with -s parameter while git format-patch.

Then I will test it.

- Alex

WARNING: multiple messages have this Message-ID (diff)
From: Alexander Aring <alex.aring@gmail.com>
To: Martin Townsend <martin.townsend@xsilon.com>
Cc: linux-bluetooth@vger.kernel.org,
	Marcel Holtmann <marcel@holtmann.org>,
	linux-wpan@vger.kernel.org,
	linux-zigbee-devel@lists.sourceforge.net
Subject: Re: [Linux-zigbee-devel] [PATCH bluetooth-next] 6lowpan: Remove ununsed dev parameter from skb_delivery_cb callback.
Date: Fri, 1 Aug 2014 11:41:46 +0200	[thread overview]
Message-ID: <20140801094144.GA11159@omega> (raw)
In-Reply-To: <53DB5A53.5000004@xsilon.com>

Hi Martin,

On Fri, Aug 01, 2014 at 10:13:55AM +0100, Martin Townsend wrote:
> This parameter is never used by any function implementing this callback.
> ---
>  include/net/6lowpan.h         | 2 +-
>  net/6lowpan/iphc.c            | 2 +-
>  net/bluetooth/6lowpan.c       | 4 ++--
>  net/ieee802154/6lowpan_rtnl.c | 5 ++---
>  4 files changed, 6 insertions(+), 7 deletions(-)
> 

I don't test it yet, but you need to add a Signed-off-by: ...

You can create this with -s parameter while git format-patch.

Then I will test it.

- Alex

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Linux-zigbee-devel mailing list
Linux-zigbee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel

  reply	other threads:[~2014-08-01  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01  9:13 [PATCH bluetooth-next] 6lowpan: Remove ununsed dev parameter from skb_delivery_cb callback Martin Townsend
2014-08-01  9:13 ` [Linux-zigbee-devel] " Martin Townsend
2014-08-01  9:41 ` Alexander Aring [this message]
2014-08-01  9:41   ` Alexander Aring
2014-08-01 10:00   ` Marc Kleine-Budde
2014-08-01 10:00     ` [Linux-zigbee-devel] " Marc Kleine-Budde

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=20140801094144.GA11159@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=linux-zigbee-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    --cc=martin.townsend@xsilon.com \
    /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.