linux-wpan.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v3 bluetooth-next] Simplify lowpan receive path so skb is freed in, lowpan_rcv when dropped.
Date: Mon, 4 Aug 2014 11:48:15 +0200	[thread overview]
Message-ID: <20140804094815.GA16774@omega> (raw)
In-Reply-To: <20140804094147.GE15334@omega>

On Mon, Aug 04, 2014 at 11:41:47AM +0200, Alexander Aring wrote:
> Martin,
> 
> On Mon, Aug 04, 2014 at 11:36:30AM +0200, Alexander Aring wrote:
> > On Mon, Aug 04, 2014 at 10:16:43AM +0100, Martin Townsend wrote:
> > > 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 appling.


- 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

  parent reply	other threads:[~2014-08-04  9:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04  8:57 [Linux-zigbee-devel] [PATCH v3 bluetooth-next] Simplify lowpan receive path so skb is freed in, lowpan_rcv when dropped Martin Townsend
2014-08-04  9:04 ` Alexander Aring
2014-08-04  9:16   ` Martin Townsend
2014-08-04  9:36     ` Alexander Aring
2014-08-04  9:41       ` Martin Townsend
2014-08-04  9:41       ` Alexander Aring
2014-08-04  9:47         ` Martin Townsend
2014-08-04  9:48         ` Alexander Aring [this message]
2014-08-04 15:35           ` Marcel Holtmann
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=20140804094815.GA16774@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).