Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/eudev: bump version to 3.1.5
Date: Sun, 22 Nov 2015 13:59:28 +0100	[thread overview]
Message-ID: <20151122135928.148e3fcd@free-electrons.com> (raw)
In-Reply-To: <1448186456-1069-1-git-send-email-bernd.kuhls@t-online.de>

Dear Bernd Kuhls,

On Sun, 22 Nov 2015 11:00:56 +0100, Bernd Kuhls wrote:
> Remove two patches applied upstream:
> https://github.com/gentoo/eudev/commit/0e2be0c217028e73073e7f9ccb010cc8b4d756db
> https://github.com/gentoo/eudev/commit/24ccb6ebc5e13a128aaedd3a2eb52eef3adf6dcd
> 
> Due to the removed patches autoreconf is not necessary anymore.
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
>  .../eudev/0002-build-sys-check-for-mallinfo.patch  | 93 ----------------------
>  .../eudev/0003-build-sys-check-for-strndupa.patch  | 69 ----------------
>  package/eudev/eudev.hash                           |  4 +-
>  package/eudev/eudev.mk                             |  7 +-
>  4 files changed, 3 insertions(+), 170 deletions(-)
>  delete mode 100644 package/eudev/0002-build-sys-check-for-mallinfo.patch
>  delete mode 100644 package/eudev/0003-build-sys-check-for-strndupa.patch

Applied to next, thanks.

We have one remaining patch for eudev, which seems quite suitable for
upstream inclusion. Could you submit it upstream?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-11-22 12:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-22 10:00 [Buildroot] [PATCH/next 1/1] package/eudev: bump version to 3.1.5 Bernd Kuhls
2015-11-22 12:59 ` Thomas Petazzoni [this message]

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=20151122135928.148e3fcd@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox