From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] lowpan-tools_0.2.2; : fix build with static libnl1
Date: Mon, 11 Apr 2011 13:41:16 +0200 [thread overview]
Message-ID: <20110411114116.GB5626@excalibur.local> (raw)
In-Reply-To: <BANLkTikvA5bhUTJ0NhKXn158Y5RhZ8V-_g@mail.gmail.com>
Hello.
On Mon, 2011-04-11 at 13:29, Anders Darander wrote:
>
> On Mon, Apr 11, 2011 at 12:57, Stefan Schmidt <stefan@datenfreihafen.org> wrote:
> > On Mon, 2011-04-11 at 11:08, Anders Darander wrote:
> >> I'll try to make a somewhat better explanation in the included patch during the evening, and I can also remove the PR bump before submitting a third revision of the patch. Hopefully I can find some time this evening.
> >
> > Thanks for this. I will test your patch and push it out after this.
>
> Thanks, I make sure to send a v3 this evening (at the latest tomorrow evening).
Thanks
> > While I still want to get lowpan-tools fixed for libnl2 I think this
> > is a good solution for the current releases.
>
> Yes, I agree with you that the correct fix is to update lowpan-tools
> to use libnl2. However, due to time constraints, we opted for the
> interim solution.
Yup, no problem. I'm going to touch the ieee802154 kernel stack and
maybe lowpan-tools the next weeks anyway I will try to squeeze in the
change to libnl2.
regards
Stefan Schmidt
next prev parent reply other threads:[~2011-04-11 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 17:27 [PATCH v2] lowpan-tools_0.2.2;: fix build with static libnl1 Anders Darander
2011-04-10 18:07 ` [PATCH v2] lowpan-tools_0.2.2; : " Anders Darander
2011-04-11 8:01 ` Martin Jansa
2011-04-11 9:08 ` Anders Darander
2011-04-11 10:57 ` Stefan Schmidt
2011-04-11 11:29 ` Anders Darander
2011-04-11 11:41 ` Stefan Schmidt [this message]
2011-04-11 17:44 ` Anders Darander
2011-04-12 7:18 ` Stefan Schmidt
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=20110411114116.GB5626@excalibur.local \
--to=stefan@datenfreihafen.org \
--cc=openembedded-devel@lists.openembedded.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.