From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Juergen Gross <jgross@suse.com>
Cc: xen-devel@lists.xenproject.org,
Anthony PERARD <anthony.perard@vates.tech>
Subject: Re: [PATCH 2/4] stubdom: remove pciutils
Date: Mon, 17 Aug 2026 18:37:13 +0200 [thread overview]
Message-ID: <aoM4ufGg8QO51XB9@end> (raw)
In-Reply-To: <2e8b1f56-6447-44c9-9555-4f1b3f0a00e8@suse.com>
Juergen Gross, le lun. 17 août 2026 10:24:02 +0200, a ecrit:
> On 17.08.26 09:48, Samuel Thibault wrote:
> > Juergen Gross, le lun. 17 août 2026 09:18:41 +0200, a ecrit:
> > > There is no user of libpci left in stubdoms.
> > >
> > > Remove libpci from the stubdom build system.
> >
> > Wouldn't it be useful to keep this for anybody who would want to drive a
> > PCI card from a stubdomain?
> >
> > I mean, in the zlib case, it's really a mere question of build & link,
> > so we don't need to ship it, people can do it themselves easily like for
> > any other library.
> >
> > But here there is actual porting work, that we'd better not lose but
> > keep shipping.
>
> This is all still available via git.
No, it is not really.
I keep reading this argument, but people will not know that something
exists in the git history, and will just assume that it does not exist
and has to be written.
Samuel
next prev parent reply other threads:[~2026-08-17 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 7:18 [PATCH 0/4] stubdom: remove building unused libraries Juergen Gross
2026-08-17 7:18 ` [PATCH 1/4] Config: update Mini-OS commit id Juergen Gross
2026-08-17 7:56 ` Jan Beulich
2026-08-17 7:18 ` [PATCH 2/4] stubdom: remove pciutils Juergen Gross
2026-08-17 7:48 ` Samuel Thibault
2026-08-17 8:24 ` Juergen Gross
2026-08-17 16:37 ` Samuel Thibault [this message]
2026-08-17 7:18 ` [PATCH 3/4] stubdom: remove build of zlib Juergen Gross
2026-08-17 7:30 ` Samuel Thibault
2026-08-17 7:18 ` [PATCH 4/4] CHANGELOG: add removal of grub-pv Juergen Gross
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=aoM4ufGg8QO51XB9@end \
--to=samuel.thibault@ens-lyon.org \
--cc=anthony.perard@vates.tech \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xenproject.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.