From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
"Andreas Färber" <afaerber@suse.de>,
"Alexander Graf" <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v3 1/5] boot: extend get_boot_devices_list() to ignore suffixes
Date: Tue, 10 Dec 2013 10:21:57 +0100 [thread overview]
Message-ID: <52A6DD35.5020302@redhat.com> (raw)
In-Reply-To: <1386660757-7505-2-git-send-email-aik@ozlabs.ru>
Il 10/12/2013 08:32, Alexey Kardashevskiy ha scritto:
> As suffixes do not make sense for sPAPR's device tree and
> there is no way to filter them out on the BusState::get_fw_dev_path
> level, let's add an ability for the external caller to specify
> whether to apply suffixes or not.
>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
SeaBIOS simply ignores unknown suffixes once it has recognized a part of
the path. Could SLOF do the same?
Paolo
next prev parent reply other threads:[~2013-12-10 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 7:32 [Qemu-devel] [PATCH v3 0/5] spapr: add bootindex support Alexey Kardashevskiy
2013-12-10 7:32 ` [Qemu-devel] [PATCH v3 1/5] boot: extend get_boot_devices_list() to ignore suffixes Alexey Kardashevskiy
2013-12-10 9:21 ` Paolo Bonzini [this message]
2013-12-11 3:56 ` Alexey Kardashevskiy
2013-12-10 7:32 ` [Qemu-devel] [PATCH v3 2/5] spapr-llan: add to boot device list Alexey Kardashevskiy
2013-12-10 7:32 ` [Qemu-devel] [PATCH v3 3/5] spapr-vio: fix firmware names Alexey Kardashevskiy
2013-12-10 7:32 ` [Qemu-devel] [PATCH v3 4/5] qdev: introduce get_fw_dev_path() callback Alexey Kardashevskiy
2013-12-10 7:32 ` [Qemu-devel] [PATCH v3 5/5] spapr: define interface to fix device pathname Alexey Kardashevskiy
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=52A6DD35.5020302@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).