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] fix eudev really not depending kernel headers >=3.9
Date: Sat, 7 Mar 2015 08:58:20 +0100	[thread overview]
Message-ID: <20150307085820.78e0d5c2@free-electrons.com> (raw)
In-Reply-To: <54FA4FD7.6080206@gmail.com>

Dear Alexey Mednyy,

On Sat, 07 Mar 2015 04:09:43 +0300, Alexey Mednyy wrote:

> > On which kernel headers version does eudev now depends? If it really
> > builds with old 2.6 kernel headers, then just get rid of this line
> > instead of commenting it out.
> I'm currently successfully built roots with headers of 2.6.36 and yes I
> used to delete this line, but forgot it (commented and started test
> build). Will fix in patch v2.

Ok, then it's alright, just remove this line.

> > Can you expand a little bit on how this can work? Maybe I missed
> > something obvious?
> I'm not sure why, but seem older kernels - reason for inclusion of
> BTRFS_IOC_DEVICES_READY in src/shared/missing.h header in eudev.

Ah, yes, indeed that's how it can work. Thanks for the clarification.

Then yes, please resend a v2 with a better title, and the "depends on"
line removed instead of commented out.

Thanks!

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

      reply	other threads:[~2015-03-07  7:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 17:09 [Buildroot] [PATCH] fix eudev really not depending kernel headers >=3.9 Alexey Mednyy
2015-03-06 22:48 ` Thomas Petazzoni
2015-03-07  1:09   ` Alexey Mednyy
2015-03-07  7:58     ` 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=20150307085820.78e0d5c2@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