All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	 openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 1/3] qemu-helper: depend on unfs3 and pseudo directly
Date: Sun, 27 Nov 2022 23:58:12 +0000	[thread overview]
Message-ID: <458025bf556060dc1e3ef56bafd564d4b998c2fb.camel@linuxfoundation.org> (raw)
In-Reply-To: <20221125211558.20985-1-alex@linutronix.de>

On Fri, 2022-11-25 at 22:15 +0100, Alexander Kanavin wrote:
> Dependencies of runqemu belong in qemu-helper; in particular
> there is no reason to scatter unfs3 all over the place, and then
> require separate steps to make it available (e.g. 'meta-ide-support').

NFS isn't really a dependency of qemu though. The thinking here was
that you could boot a real board onto an NFS mount from your local
system for development purposes. That is why it was being included as
an SDK tool.

Perhaps we should just add it to qemu helper as well to simplify the
runqemu case?

Cheers,

Richard


  parent reply	other threads:[~2022-11-27 23:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 21:15 [PATCH 1/3] qemu-helper: depend on unfs3 and pseudo directly Alexander Kanavin
2022-11-25 21:15 ` [PATCH 2/3] runqemu: do not hardcode the ip address of the nfs server when using tap Alexander Kanavin
2022-11-25 21:15 ` [PATCH 3/3] selftest/runqemu: reenable the nfs rootfs test Alexander Kanavin
2022-11-27 23:58 ` Richard Purdie [this message]
2022-11-28  9:54   ` [OE-core] [PATCH 1/3] qemu-helper: depend on unfs3 and pseudo directly Alexander Kanavin
2022-11-28 10:15     ` Richard Purdie

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=458025bf556060dc1e3ef56bafd564d4b998c2fb.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.