qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: Hao Wu <wuhaotsh@google.com>, Bin Meng <bin.meng@windriver.com>,
	Alistair Francis <alistair.francis@wdc.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Qemu-block <qemu-block@nongnu.org>
Subject: Re: does drive_get_next(IF_NONE) make sense?
Date: Wed, 3 Nov 2021 10:19:26 +0100	[thread overview]
Message-ID: <e7ec3afc-6db9-822e-5a5e-dee7c4db8f34@redhat.com> (raw)
In-Reply-To: <87r1bxzl5c.fsf@dusky.pond.sub.org>

On 03/11/2021 09.41, Markus Armbruster wrote:
> Peter Maydell <peter.maydell@linaro.org> writes:
> 
>> Does it make sense for a device/board to do drive_get_next(IF_NONE) ?
> 
> Short answer: hell, no!  ;)

Would it make sense to add an "assert(type != IF_NONE)" to drive_get() to 
avoid such mistakes in the future?

  Thomas



  reply	other threads:[~2021-11-03  9:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 15:14 does drive_get_next(IF_NONE) make sense? Peter Maydell
2021-11-02 15:28 ` Philippe Mathieu-Daudé
2021-11-03  8:41 ` Markus Armbruster
2021-11-03  9:19   ` Thomas Huth [this message]
2021-11-12 13:33     ` Markus Armbruster
2021-11-14 17:16       ` Peter Maydell
2021-11-15  5:31         ` Markus Armbruster
2021-11-15  7:12           ` Alistair Francis
2021-11-15 16:09             ` Thomas Huth
2021-11-18 13:03               ` Alistair Francis
2021-11-18 13:20                 ` Peter Maydell
2021-11-15 13:24           ` Kevin Wolf
2021-11-15 13:31             ` Peter Maydell
2021-11-15 15:13               ` Kevin Wolf
2021-11-15 15:28               ` Markus Armbruster

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=e7ec3afc-6db9-822e-5a5e-dee7c4db8f34@redhat.com \
    --to=thuth@redhat.com \
    --cc=alistair.francis@wdc.com \
    --cc=armbru@redhat.com \
    --cc=bin.meng@windriver.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wuhaotsh@google.com \
    /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).