From: Alex Williamson <alex.williamson@redhat.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Kirti Wankhede <kwankhede@nvidia.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
KVM ML <kvm@vger.kernel.org>,
KERNEL ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] samples: vfio-mdev: mtty.c: delete MODULE_VERSION
Date: Mon, 2 Jun 2025 09:43:34 -0600 [thread overview]
Message-ID: <20250602094334.4995ea23.alex.williamson@redhat.com> (raw)
In-Reply-To: <20250531161836.102346-1-xose.vazquez@gmail.com>
On Sat, 31 May 2025 18:18:36 +0200
Xose Vazquez Perez <xose.vazquez@gmail.com> wrote:
> Reminiscence of ancient times when modules were developed outside the kernel.
s/Reminiscence/Reminiscent/
I think there are likely better arguments that could be made for
removal though, ex. citing specific policies or discussions.
> Cc: Kirti Wankhede <kwankhede@nvidia.com>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: KVM ML <kvm@vger.kernel.org>
> Cc: KERNEL ML <linux-kernel@vger.kernel.org>
Signed-off-by?
See Developer's Certificate of Origin:
Documentation/process/submitting-patches.rst
Thanks,
Alex
> ---
> samples/vfio-mdev/mtty.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/samples/vfio-mdev/mtty.c b/samples/vfio-mdev/mtty.c
> index 59eefe2fed10..f9f7472516c9 100644
> --- a/samples/vfio-mdev/mtty.c
> +++ b/samples/vfio-mdev/mtty.c
> @@ -35,7 +35,6 @@
> * #defines
> */
>
> -#define VERSION_STRING "0.1"
> #define DRIVER_AUTHOR "NVIDIA Corporation"
>
> #define MTTY_CLASS_NAME "mtty"
> @@ -2057,5 +2056,4 @@ module_exit(mtty_dev_exit)
>
> MODULE_LICENSE("GPL v2");
> MODULE_DESCRIPTION("Test driver that simulate serial port over PCI");
> -MODULE_VERSION(VERSION_STRING);
> MODULE_AUTHOR(DRIVER_AUTHOR);
prev parent reply other threads:[~2025-06-02 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-31 16:18 Xose Vazquez Perez
2025-06-02 15:43 ` Alex Williamson [this message]
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=20250602094334.4995ea23.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xose.vazquez@gmail.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
all inboxes | Powered by JetHome®