Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libnl: bump to version 3.2.17
Date: Fri, 04 Jan 2013 17:52:57 -0300	[thread overview]
Message-ID: <50E74129.5050105@zacarias.com.ar> (raw)
In-Reply-To: <87hamwn0br.fsf@dell.be.48ers.dk>

On 01/04/2013 05:46 PM, Peter Korsgaard wrote:
>  Gustavo> -LIBNL_VERSION = 3.2.16
>  Gustavo> +LIBNL_VERSION = 3.2.17
> 
> Committed, thanks.
> 
> Could you have a look at http://patchwork.ozlabs.org/patch/208318/ ?

Yes, it's no longer required, part of 3.2.17
Seems many people had issues with old enough headers and upstream
decided to release .17 with those patches to fit it.
Also fixes our previous autobuild errors which i assume went away when
Thomas probably upgraded to new toolchain versions.
We are talking about <2.6.32 headers IIRC.
Regards.

  reply	other threads:[~2013-01-04 20:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 20:42 [Buildroot] [PATCH] libnl: bump to version 3.2.17 Gustavo Zacarias
2013-01-04 20:46 ` Peter Korsgaard
2013-01-04 20:52   ` Gustavo Zacarias [this message]
2013-01-04 21:10     ` Peter Korsgaard
2013-01-08 17:15 ` Thomas Petazzoni
2013-01-08 17:46   ` Gustavo Zacarias

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=50E74129.5050105@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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