From: Bobby Eshleman <bobbyeshleman@gmail.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Shuah Khan <shuah@kernel.org>,
kvm@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v7] selftests/vsock: add initial vmtest.sh for vsock
Date: Tue, 20 May 2025 09:33:05 -0700 [thread overview]
Message-ID: <aCyuwa8x9ClTOM+Z@devbig793.prn5.facebook.com> (raw)
In-Reply-To: <w6aizeb2i5m52e2ifqcikgwdbrkkbc46sf4hx5b6jsm7o4drio@n3dzlatb426s>
On Tue, May 20, 2025 at 01:09:25PM +0200, Stefano Garzarella wrote:
> On Tue, May 20, 2025 at 12:58:18PM +0200, Paolo Abeni wrote:
> > On 5/20/25 10:24 AM, Stefano Garzarella wrote:
> >
> > Still it could be worthy to re-introduce (behind a command line option)
> > the ability to build the kernel as per Stefano request, to fit his
> > existing workflow (sorry for the partial back and forth).
>
> If that's possible, I'd appreciate it (not a strong opinion). Otherwise if
> we don't, I'd say take the use of the direct script out of the commit
> messaging, because to me it's confusing if we don't plan to use it without
> the selftest infrastructure.
>
> Thanks,
> Stefano
>
No problem at all to add it back in. It's a nice feature to have for dev
workflows too.
Best,
Bobby
next prev parent reply other threads:[~2025-05-20 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 22:00 [PATCH net-next v7] selftests/vsock: add initial vmtest.sh for vsock Bobby Eshleman
2025-05-20 8:24 ` Stefano Garzarella
2025-05-20 10:58 ` Paolo Abeni
2025-05-20 11:09 ` Stefano Garzarella
2025-05-20 16:33 ` Bobby Eshleman [this message]
2025-05-20 16:31 ` Bobby Eshleman
2025-05-20 11:24 ` Paolo Abeni
2025-05-20 16:09 ` Bobby Eshleman
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=aCyuwa8x9ClTOM+Z@devbig793.prn5.facebook.com \
--to=bobbyeshleman@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=shuah@kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
/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.