All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Martin Townsend <martin.townsend@xsilon.com>,
	linux-zigbee-devel@lists.sourceforge.net,
	BlueZ development <linux-bluetooth@vger.kernel.org>,
	linux-wpan@vger.kernel.org
Subject: Re: [PATCH v3 bluetooth-next] Simplify lowpan receive path so skb is freed in, lowpan_rcv when dropped.
Date: Mon, 4 Aug 2014 17:41:10 +0200	[thread overview]
Message-ID: <20140804154108.GA16842@omega> (raw)
In-Reply-To: <215A7DE1-74A1-4454-8DDF-98E960F7260D@holtmann.org>

Hi Marcel,

On Mon, Aug 04, 2014 at 08:35:48AM -0700, Marcel Holtmann wrote:
> Hi Alex,
> 
> >>>> The changes were made to a clone of bluetooth-next, do I have the right repository?
> >>>> 
> >>>> martin@martin-HP-ProDesk-490-G1-MT:~/workspace/bluetooth-next$ git ls-remote
> >>>> From git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git
> >>>> 
> >>> yes, but maybe it's a little bit outdated. Try to update it, on top of
> >>> git log should be the patches:
> >>> 
> >>> http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/log/
> >>> 
> >> 
> >> I think I know now why it fails. This patch depends on your previous patch
> >> ("6lowpan: Remove ununsed dev parameter from skb_delivery_cb
> >> callback."), otherwise I get merge conflicts.
> >> 
> >> Normally you need to send this in a series of patches to avoid something
> >> like this. Now you need to wait until your patch ("6lowpan: Remove
> >> ununsed dev parameter from skb_delivery_cb callback.") go into the
> >> bluetooth-next tree.
> >> 
> > 
> > Or write in the patch file under the "---" lines:
> > 
> > "This patch depends on..." if Marcel can deal with this kind of
> > dependency notification.
> > 
> > Otherwise nobody knows what's going on now and want to apply it on
> > bluetooth-next, like me...
> > 
> > 
> > btw. lines after "---" will be ignored by applying.
> 
> so I am fine either way. You can mention this in the section after --- or you just send a patch set that is versioned [PATCH x/y].
> 
> Just right now I am delaying applying net/6lowpan/ patches until John, Dave and I have resolved the merge conflicts for getting the current patches into net-next. After that I will start actively applying these patches.
> 

Thanks for explanation and carry about the merge conflicts. Sorry about
that there exists now a huge merge conflicts, but this should never
happen if all 802.15.4/6lowpan stuff goes into bluetooth.

- Alex

WARNING: multiple messages have this Message-ID (diff)
From: Alexander Aring <alex.aring@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-wpan@vger.kernel.org,
	linux-zigbee-devel@lists.sourceforge.net,
	BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [Linux-zigbee-devel] [PATCH v3 bluetooth-next] Simplify lowpan receive path so skb is freed in, lowpan_rcv when dropped.
Date: Mon, 4 Aug 2014 17:41:10 +0200	[thread overview]
Message-ID: <20140804154108.GA16842@omega> (raw)
In-Reply-To: <215A7DE1-74A1-4454-8DDF-98E960F7260D@holtmann.org>

Hi Marcel,

On Mon, Aug 04, 2014 at 08:35:48AM -0700, Marcel Holtmann wrote:
> Hi Alex,
> 
> >>>> The changes were made to a clone of bluetooth-next, do I have the right repository?
> >>>> 
> >>>> martin@martin-HP-ProDesk-490-G1-MT:~/workspace/bluetooth-next$ git ls-remote
> >>>> From git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git
> >>>> 
> >>> yes, but maybe it's a little bit outdated. Try to update it, on top of
> >>> git log should be the patches:
> >>> 
> >>> http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/log/
> >>> 
> >> 
> >> I think I know now why it fails. This patch depends on your previous patch
> >> ("6lowpan: Remove ununsed dev parameter from skb_delivery_cb
> >> callback."), otherwise I get merge conflicts.
> >> 
> >> Normally you need to send this in a series of patches to avoid something
> >> like this. Now you need to wait until your patch ("6lowpan: Remove
> >> ununsed dev parameter from skb_delivery_cb callback.") go into the
> >> bluetooth-next tree.
> >> 
> > 
> > Or write in the patch file under the "---" lines:
> > 
> > "This patch depends on..." if Marcel can deal with this kind of
> > dependency notification.
> > 
> > Otherwise nobody knows what's going on now and want to apply it on
> > bluetooth-next, like me...
> > 
> > 
> > btw. lines after "---" will be ignored by applying.
> 
> so I am fine either way. You can mention this in the section after --- or you just send a patch set that is versioned [PATCH x/y].
> 
> Just right now I am delaying applying net/6lowpan/ patches until John, Dave and I have resolved the merge conflicts for getting the current patches into net-next. After that I will start actively applying these patches.
> 

Thanks for explanation and carry about the merge conflicts. Sorry about
that there exists now a huge merge conflicts, but this should never
happen if all 802.15.4/6lowpan stuff goes into bluetooth.

- Alex

------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
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-04 15:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04  8:57 [PATCH v3 bluetooth-next] Simplify lowpan receive path so skb is freed in, lowpan_rcv when dropped Martin Townsend
2014-08-04  8:57 ` [Linux-zigbee-devel] " Martin Townsend
2014-08-04  9:04 ` Alexander Aring
2014-08-04  9:04   ` [Linux-zigbee-devel] " Alexander Aring
2014-08-04  9:16   ` Martin Townsend
2014-08-04  9:16     ` [Linux-zigbee-devel] " Martin Townsend
2014-08-04  9:36     ` Alexander Aring
2014-08-04  9:36       ` [Linux-zigbee-devel] " Alexander Aring
2014-08-04  9:41       ` Martin Townsend
2014-08-04  9:41         ` [Linux-zigbee-devel] " Martin Townsend
2014-08-04  9:41       ` Alexander Aring
2014-08-04  9:41         ` [Linux-zigbee-devel] " Alexander Aring
2014-08-04  9:47         ` Martin Townsend
2014-08-04  9:47           ` [Linux-zigbee-devel] " Martin Townsend
2014-08-04  9:48         ` Alexander Aring
2014-08-04  9:48           ` [Linux-zigbee-devel] " Alexander Aring
2014-08-04 15:35           ` Marcel Holtmann
2014-08-04 15:35             ` [Linux-zigbee-devel] " Marcel Holtmann
2014-08-04 15:41             ` Alexander Aring [this message]
2014-08-04 15:41               ` Alexander Aring

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=20140804154108.GA16842@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.