Linux Media Controller development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Matthew Majewski <mattwmajewski@gmail.com>,
	Uwe Kleine-Konig <u.kleine-koenig@baylibre.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] media: vim2m: print device name after registering device
Date: Thu, 20 Feb 2025 09:27:47 -0700	[thread overview]
Message-ID: <fdd0356f-d91e-400e-9598-d34e0862c9cb@linuxfoundation.org> (raw)
In-Reply-To: <61bd42742ff8a8e5f409b0f2ccc4ab8875dfe7a4.camel@gmail.com>

On 2/20/25 08:29, Matthew Majewski wrote:
> On Wed, 2025-02-19 at 17:21 -0700, Shuah Khan wrote:
>> On 2/19/25 14:58, Uwe Kleine-Konig wrote:
>>> On Wed, Feb 19, 2025 at 02:05:01PM -0500, Matthew Majewski wrote:
>>>> Move the v4l2_info() call displaying the video device name after
>>>> the
>>>> device is actually registered.
>>>>
>>>> This fixes a bug where the driver was always displaying
>>>> "/dev/video0"
>>>> since it was reading from the vfd before it was registered.
>>>>
>>>> Signed-off-by: Matthew Majewski <mattwmajewski@gmail.com>
>>>
>>> A Fixes: tag would be great.
>>
>> Matthew, there is no need to resend the patch. Just send me the
>> Fixes tag and I will update the repo.
>>
>>
> 
> Ok, here is the fixes tag:
> 
> Fixes: cf7f34777a5b4100a ("media: vim2m: Register video device after
> setting up internals")
> 

Thank you. commit is now updated.

thanks,
-- Shuah


  reply	other threads:[~2025-02-20 16:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19 19:05 [PATCH] media: vim2m: print device name after registering device Matthew Majewski
2025-02-19 21:11 ` Shuah Khan
2025-02-19 21:58 ` Uwe Kleine-Konig
2025-02-20  0:21   ` Shuah Khan
2025-02-20 15:29     ` Matthew Majewski
2025-02-20 16:27       ` Shuah Khan [this message]
2025-03-06  8:37         ` Hans Verkuil
2025-03-06 16:01           ` Shuah Khan

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=fdd0356f-d91e-400e-9598-d34e0862c9cb@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mattwmajewski@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=u.kleine-koenig@baylibre.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