From: Shuah Khan <skhan@linuxfoundation.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>, linux-media@vger.kernel.org
Cc: Kieran Bingham <kieran.bingham@ideasonboard.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 2/2] media: vimc: Don't explicitly set bus_info
Date: Tue, 9 Jan 2024 12:37:39 -0700 [thread overview]
Message-ID: <8de79d85-d70d-44ec-9700-5f5356d9c393@linuxfoundation.org> (raw)
In-Reply-To: <20231129141545.87461-3-sakari.ailus@linux.intel.com>
On 11/29/23 07:15, Sakari Ailus wrote:
> The platform device name is already set by V4L2 and MC frameworks for
> media device bus_info and V4L2 querycap bus_info fields. Don't do it in
> the driver.
>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
> drivers/media/test-drivers/vimc/vimc-capture.c | 2 --
> drivers/media/test-drivers/vimc/vimc-core.c | 2 --
> 2 files changed, 4 deletions(-)
>
> diff --git a/drivers/media/test-drivers/vimc/vimc-capture.c b/drivers/media/test-drivers/vimc/vimc-capture.c
> index aa944270e716..1e7cc7c980f9 100644
> --- a/drivers/media/test-drivers/vimc/vimc-capture.c
> +++ b/drivers/media/test-drivers/vimc/vimc-capture.c
> @@ -57,8 +57,6 @@ static int vimc_capture_querycap(struct file *file, void *priv,
> {
> strscpy(cap->driver, VIMC_PDEV_NAME, sizeof(cap->driver));
> strscpy(cap->card, KBUILD_MODNAME, sizeof(cap->card));
> - snprintf(cap->bus_info, sizeof(cap->bus_info),
> - "platform:%s", VIMC_PDEV_NAME);
>
> return 0;
> }
> diff --git a/drivers/media/test-drivers/vimc/vimc-core.c b/drivers/media/test-drivers/vimc/vimc-core.c
> index af127476e920..2a924abd0ebc 100644
> --- a/drivers/media/test-drivers/vimc/vimc-core.c
> +++ b/drivers/media/test-drivers/vimc/vimc-core.c
> @@ -366,8 +366,6 @@ static int vimc_probe(struct platform_device *pdev)
> /* Initialize media device */
> strscpy(vimc->mdev.model, VIMC_MDEV_MODEL_NAME,
> sizeof(vimc->mdev.model));
> - snprintf(vimc->mdev.bus_info, sizeof(vimc->mdev.bus_info),
> - "platform:%s", VIMC_PDEV_NAME);
> vimc->mdev.dev = &pdev->dev;
> media_device_init(&vimc->mdev);
>
Sorry this seems to have been lost in inbox.
Acked-by: Shuah Khan <skhan@linuxfoundation.org>
thanks,
-- Shuah
prev parent reply other threads:[~2024-01-09 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 14:15 [PATCH 0/2] Don't set bus info for test drivers Sakari Ailus
2023-11-29 14:15 ` [PATCH 1/2] media: vivid: Don't explicitly set bus_info Sakari Ailus
2023-11-29 14:26 ` Hans Verkuil
2023-11-29 15:49 ` Sakari Ailus
2023-11-29 14:15 ` [PATCH 2/2] media: vimc: " Sakari Ailus
2024-01-09 19:37 ` Shuah Khan [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=8de79d85-d70d-44ec-9700-5f5356d9c393@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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