All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/5] libnl: bump to version 3.2.3
Date: Sat, 3 Dec 2011 19:48:47 +0100	[thread overview]
Message-ID: <20111203194847.4ece94f7@skate> (raw)
In-Reply-To: <1322931812-10734-1-git-send-email-zonque@gmail.com>

Hello Daniel,

Le Sat,  3 Dec 2011 18:03:28 +0100,
Daniel Mack <zonque@gmail.com> a ?crit :

> This newer version splits the library code into libnl, libnl-route,
> libnl-genl and libnl-nf, each individually selectable via pkgconfig.

Thanks for those updates. I have a couple of comments/questions:

 * It would be nice if you could send each version of the patch set
   with a cover e-mail (a 0/5 e-mail) that contains a changelog between
   the different versions of your patchset (i.e, what changed from v2
   to v3, from v3 to v4)

 * Many of your patches are introducing patches for various components.
   Have you submitted those to the respective upstream projects ?

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2011-12-03 18:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-03 17:03 [Buildroot] [PATCH v4 1/5] libnl: bump to version 3.2.3 Daniel Mack
2011-12-03 17:03 ` [Buildroot] [PATCH v4 2/5] hostapd: fix build with new libnl-3 Daniel Mack
2011-12-03 17:03 ` [Buildroot] [PATCH v4 3/5] wpa_supplicant: " Daniel Mack
2011-12-03 17:03 ` [Buildroot] [PATCH v4 4/5] iw: using the git version fixes " Daniel Mack
2011-12-03 17:03 ` [Buildroot] [PATCH v4 5/5] kismet: fix " Daniel Mack
2011-12-03 18:48 ` Thomas Petazzoni [this message]
2011-12-03 19:07   ` [Buildroot] [PATCH v4 1/5] libnl: bump to version 3.2.3 Daniel Mack
2011-12-26 16:02 ` Peter Korsgaard

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=20111203194847.4ece94f7@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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 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.