Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Stefan Ott via buildroot <buildroot@buildroot.org>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>,
	Bernd Kuhls <bernd.kuhls@t-online.de>,
	Stefan Ott <stefan@ott.net>
Subject: Re: [Buildroot] [PATCH v2 1/1] package/eudev: fix compile-time issue with very old kernel headers
Date: Sun, 23 Apr 2023 11:28:44 +0200	[thread overview]
Message-ID: <87jzy36j77.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20230412224038.109749-1-stefan@ott.net> (Stefan Ott via buildroot's message of "Thu, 13 Apr 2023 00:40:39 +0200")

>>>>> "Stefan" == Stefan Ott via buildroot <buildroot@buildroot.org> writes:

 > Kernel versions prior to 3.4 did not have V4L2_CAP_DEVICE_CAPS and
 > compiling against such a kernel will fail.

 > This patch introduces a version check and makes eudev fall back to
 > v2cap.capabilities on these kernels.

 > Upstream: https://github.com/eudev-project/eudev/pull/247
 > Signed-off-by: Stefan Ott <stefan@ott.net>
 > ---
 > Changes v1 -> v2 (suggested by Arnout Vandecappelle):
 > - Clarified description to talk about kernel *headers*
 > - Use a git-formatted patch instead
 > - Added a Signed-off-by line
 > - Added upstream reference

Committed to 2023.02.x and 2022.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-04-23  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 22:40 [Buildroot] [PATCH v2 1/1] package/eudev: fix compile-time issue with very old kernel headers Stefan Ott via buildroot
2023-04-15 12:51 ` Yann E. MORIN
2023-04-23  9:28 ` Peter Korsgaard [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=87jzy36j77.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=bernd.kuhls@t-online.de \
    --cc=buildroot@buildroot.org \
    --cc=eric.le.bihan.dev@free.fr \
    --cc=stefan@ott.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