From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Šerif Rami" <ramiserifpersia@gmail.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Wesley Cheng <quic_wcheng@quicinc.com>
Subject: Re: [RFC PATCH v3] ALSA: usb-audio: Add support for TASCAM US-144MKII
Date: Sun, 3 Aug 2025 21:49:48 +0100 [thread overview]
Message-ID: <2025080341-usher-tastiness-0507@gregkh> (raw)
In-Reply-To: <20250803203409.17005-1-ramiserifpersia@gmail.com>
On Sun, Aug 03, 2025 at 10:34:09PM +0200, Šerif Rami wrote:
> +/**
> + * driver_version_show() - Sysfs attribute to display the driver version.
> + * @dev: Pointer to the device structure.
> + * @attr: Pointer to the device attribute structure.
> + * @buf: Buffer to write the version string into.
> + *
> + * This function is a sysfs callback that provides the current driver version
> + * string to user-space when the 'driver_version' attribute is read.
> + *
> + * Return: The number of bytes written to the buffer.
> + */
> +static ssize_t driver_version_show(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + return sysfs_emit(buf, "%s\n", DRIVER_VERSION);
> +}
> +static DEVICE_ATTR_RO(driver_version);
The driver version makes no sense when it is in the kernel tree, so this
can be removed.
Also, all sysfs files need to be documented in Documentation/ABI/
thanks,
greg k-h
next prev parent reply other threads:[~2025-08-03 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-03 20:34 [RFC PATCH v3] ALSA: usb-audio: Add support for TASCAM US-144MKII Šerif Rami
2025-08-03 20:49 ` Greg Kroah-Hartman [this message]
2025-08-03 21:58 ` Šerif Rami
2025-08-08 9:53 ` Takashi Iwai
2025-08-08 11:14 ` [PATCH " Šerif Rami
2025-08-08 11:47 ` Takashi Iwai
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=2025080341-usher-tastiness-0507@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=quic_wcheng@quicinc.com \
--cc=ramiserifpersia@gmail.com \
--cc=tiwai@suse.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