Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libpciaccess: add dependency on hwdata
Date: Thu, 29 Mar 2018 21:05:28 +0200	[thread overview]
Message-ID: <87efk28zyf.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180329175202.GA23440@scaer> (Yann E. MORIN's message of "Thu,  29 Mar 2018 19:52:02 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

Hi,

 >> It is required by libvirt[1] to show device names when we use virtual
 >> machine manager to add hardware via PCI passthrough, otherwise only
 >> the PCI bus information (slot, port, function) is shown.

 > Then I would say that it is not _required_. It may be _needed_, but it
 > is not mandatory; it just makes it a little bit more user-friendly.

 > Thus, I would say that we do not want to enforce this dependency,
 > because it still works without it.

And if it IS required when using libvirt with pci passthrough, but not
necessarily for other users of libpciaccess, then we can make libvirt
select it.

In the general case for nice-to-have-but-not-absolutely-required
dependencies we don't have a solution in Buildroot today except for a
note in the help text. Upstream kconfig has recently added the imply
keyword which could be used to implement this, but we would need to sync
our kconfig with upstream for that.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-03-29 19:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-28 23:52 [Buildroot] [PATCH] libpciaccess: add dependency on hwdata Carlos Santos
2018-03-29 14:05 ` Peter Korsgaard
2018-03-29 16:41   ` Carlos Santos
2018-03-29 17:52     ` Yann E. MORIN
2018-03-29 19:05       ` Peter Korsgaard [this message]
2018-04-03  1:38         ` Carlos Santos
2018-04-28 21:39           ` 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=87efk28zyf.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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