From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1 v3] eudev: fix dependency on kernel headers version
Date: Mon, 9 Mar 2015 13:45:25 +0200 [thread overview]
Message-ID: <20150309114525.GI2518@tarshish> (raw)
In-Reply-To: <1425901067-27699-1-git-send-email-swexru@gmail.com>
Hi Alexey,
On Mon, Mar 09, 2015 at 02:37:47PM +0300, Alexey Mednyy wrote:
> a/package/eudev/0001-configure.ac-don-t-die-on-missing-linux-btrfs.h-fixe.patch
> b/package/eudev/0001-configure.ac-don-t-die-on-missing-linux-btrfs.h-fixe.patch
> new file mode 100644
> index 0000000..a749b08
> --- /dev/null
> +++ b/package/eudev/0001-configure.ac-don-t-die-on-missing-linux-btrfs.h-fixe.patch
> @@ -0,0 +1,37 @@
> +From 6740579367ddd2ce0b315863cdb92d34d1d693c7 Mon Sep 17 00:00:00 2001
> +From: "Anthony G. Basile" <blueness@gentoo.org>
> +Date: Sun, 16 Nov 2014 13:40:43 -0500
> +Subject: [PATCH] configure.ac: don't die on missing linux/btrfs.h, fixes issue
> + #100
> +
> +Signed-off-by: Anthony G. Basile <blueness@gentoo.org>
Since this patch seems to be backported from upstream, its description should
contain a reference to upstream. In this case saying something like "upstream
commit 6740579367d" should be enough.
Sorry for not mentioning it previously.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-03-09 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 11:37 [Buildroot] [PATCH 1/1 v3] eudev: fix dependency on kernel headers version Alexey Mednyy
2015-03-09 11:45 ` Baruch Siach [this message]
2015-03-09 13:06 ` Thomas Petazzoni
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=20150309114525.GI2518@tarshish \
--to=baruch@tkos.co.il \
--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