mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	"Carlos E. C. Barbosa" <climacobarbosacee@gmail.com>,
	Helen Koike <helen.koike@collabora.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v6] media: vimc: get pixformat info from v4l2_format_info
Date: Tue, 26 Apr 2022 09:34:28 -0600	[thread overview]
Message-ID: <07f415c4-addb-73e8-6604-60e7eeb63abf@linuxfoundation.org> (raw)
In-Reply-To: <3665efc7-0b47-1adf-5639-93229af04e95@xs4all.nl>

Hi Carlos,

On 4/26/22 3:02 AM, Hans Verkuil wrote:
> Hi Carlos,
> 
> On 11/03/2022 12:16, Carlos E. C. Barbosa wrote:
>> Removes overlapping structures
>>
>> Repurposes vimc_pix_map to strictly mapping formats, making it
>> a local structure.
>>
>> Replaces all of its functions and remaps the calls to the matching
>> v4l2_format_info.
>>
>> ---
>>
>> Changes in v6:
>> - replace all vimc_pix_map returning functions with v4l2_format_info
>>    ones (as previously suggested by Dafna)
>> - adds is_on_table functions to verify support (to be used only when
>>    no other info is required)
>>
>> Changes in v5:
>> - .bayer member was removed and replaced by v4l2 functions calls
>>
>> Changes in v4:
>> - Unused variables were removed
>>
>> Changes in v3:
>> - Change declaration order of variables and some minor style changes
>>
>> Changes in v2:
>> - Const qualifiers are not removed
>> - Bayer flag is kept
>> - Unnecessary changes are not made anymore
>>
>> v4l2-compliance -m /dev/media0 output:
>> https://pastebin.com/BRjMP3wP
>>
>> Signed-off-by: Carlos E. C. Barbosa <barbosa.carlos.ec@gmail.com>
> 
> Your Signed-off-by should go before the '---'.
> 
> Also, it doesn't match your 'From' email.
> 
> Regards,
> 
> 	Hans
> 
>
Sorry for the delay on this. In addition to Han's comments,
please provide more information in your commit log on the
changes and how they help in more detail. Are these changes
fix any problems you may have found.

thanks,
-- Shuah

      reply	other threads:[~2022-04-26 15:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 11:16 Carlos E. C. Barbosa
2022-04-26  9:02 ` Hans Verkuil
2022-04-26 15:34   ` 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=07f415c4-addb-73e8-6604-60e7eeb63abf@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=climacobarbosacee@gmail.com \
    --cc=helen.koike@collabora.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    /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®