From: Shuah Khan <shuahkh@osg.samsung.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
kgene@kernel.org, mchehab@osg.samsung.com, andrzej.p@samsung.com,
hans.verkuil@cisco.com, javier@osg.samsung.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] media: Doc add missing documentation for samsung,exynos4212-jpeg
Date: Fri, 15 Jul 2016 16:09:26 -0600 [thread overview]
Message-ID: <57895F16.7010101@osg.samsung.com> (raw)
In-Reply-To: <5788AEE4.8080606@samsung.com>
Hi Krzysztof and Jacek,
Thanks for the review.
On 07/15/2016 03:37 AM, Jacek Anaszewski wrote:
> On 07/15/2016 11:30 AM, Krzysztof Kozlowski wrote:
>> On 07/15/2016 11:18 AM, Jacek Anaszewski wrote:
>>> On 07/15/2016 10:33 AM, Krzysztof Kozlowski wrote:
>>>> On 07/15/2016 10:28 AM, Jacek Anaszewski wrote:
>>>>> On 07/15/2016 10:17 AM, Krzysztof Kozlowski wrote:
>>>>>> On 07/15/2016 10:14 AM, Jacek Anaszewski wrote:
>>>>>>>> However if these compatibles are exactly equal then
>>>>>>>> only one should be preferred. It makes everything easier. Second
>>>>>>>> can be
>>>>>>>> still documented e.g. as deprecated.
>>>>>>>
>>>>>>> Still, both of them are present in the driver. Shouldn't it be
>>>>>>> reflected
>>>>>>> in the documentation?
>>>>>>
>>>>>> Right, it is a good practice, so how about:
>>>>>>
>>>>>> - compatible : should be one of:
>>>>>> "samsung,s5pv210-jpeg", "samsung,exynos3250-jpeg",
>>>>>> "samsung,exynos4210-jpeg", "samsung,exynos5420-jpeg",
>>>>>> "samsung,exynos5433-jpeg";
>>>>>>
>>>>>> Deprecated: "samsung,exynos4212-jpeg"
>>>>>>
>>>>>> (or any other formatting)
>>>>>> plus update to DTS changing it to 4210?
I am sending the v2 doc patch that adds samsung,exynos4212-jpeg as
deprecated to begin with.
thanks,
-- Shuah
WARNING: multiple messages have this Message-ID (diff)
From: shuahkh@osg.samsung.com (Shuah Khan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] media: Doc add missing documentation for samsung,exynos4212-jpeg
Date: Fri, 15 Jul 2016 16:09:26 -0600 [thread overview]
Message-ID: <57895F16.7010101@osg.samsung.com> (raw)
In-Reply-To: <5788AEE4.8080606@samsung.com>
Hi Krzysztof and Jacek,
Thanks for the review.
On 07/15/2016 03:37 AM, Jacek Anaszewski wrote:
> On 07/15/2016 11:30 AM, Krzysztof Kozlowski wrote:
>> On 07/15/2016 11:18 AM, Jacek Anaszewski wrote:
>>> On 07/15/2016 10:33 AM, Krzysztof Kozlowski wrote:
>>>> On 07/15/2016 10:28 AM, Jacek Anaszewski wrote:
>>>>> On 07/15/2016 10:17 AM, Krzysztof Kozlowski wrote:
>>>>>> On 07/15/2016 10:14 AM, Jacek Anaszewski wrote:
>>>>>>>> However if these compatibles are exactly equal then
>>>>>>>> only one should be preferred. It makes everything easier. Second
>>>>>>>> can be
>>>>>>>> still documented e.g. as deprecated.
>>>>>>>
>>>>>>> Still, both of them are present in the driver. Shouldn't it be
>>>>>>> reflected
>>>>>>> in the documentation?
>>>>>>
>>>>>> Right, it is a good practice, so how about:
>>>>>>
>>>>>> - compatible : should be one of:
>>>>>> "samsung,s5pv210-jpeg", "samsung,exynos3250-jpeg",
>>>>>> "samsung,exynos4210-jpeg", "samsung,exynos5420-jpeg",
>>>>>> "samsung,exynos5433-jpeg";
>>>>>>
>>>>>> Deprecated: "samsung,exynos4212-jpeg"
>>>>>>
>>>>>> (or any other formatting)
>>>>>> plus update to DTS changing it to 4210?
I am sending the v2 doc patch that adds samsung,exynos4212-jpeg as
deprecated to begin with.
thanks,
-- Shuah
next prev parent reply other threads:[~2016-07-15 22:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 20:01 [PATCH] media: Doc add missing documentation for samsung,exynos4212-jpeg Shuah Khan
2016-07-14 20:01 ` [PATCH] media: Doc add missing documentation for samsung, exynos4212-jpeg Shuah Khan
2016-07-15 6:25 ` [PATCH] media: Doc add missing documentation for samsung,exynos4212-jpeg Jacek Anaszewski
2016-07-15 6:25 ` Jacek Anaszewski
2016-07-15 7:28 ` Krzysztof Kozlowski
2016-07-15 7:28 ` Krzysztof Kozlowski
2016-07-15 8:14 ` Jacek Anaszewski
2016-07-15 8:14 ` Jacek Anaszewski
2016-07-15 8:17 ` Krzysztof Kozlowski
2016-07-15 8:17 ` Krzysztof Kozlowski
2016-07-15 8:28 ` Jacek Anaszewski
2016-07-15 8:28 ` Jacek Anaszewski
2016-07-15 8:33 ` Krzysztof Kozlowski
2016-07-15 8:33 ` Krzysztof Kozlowski
2016-07-15 9:18 ` Jacek Anaszewski
2016-07-15 9:18 ` Jacek Anaszewski
2016-07-15 9:30 ` Krzysztof Kozlowski
2016-07-15 9:30 ` Krzysztof Kozlowski
2016-07-15 9:37 ` Jacek Anaszewski
2016-07-15 9:37 ` Jacek Anaszewski
2016-07-15 22:09 ` Shuah Khan [this message]
2016-07-15 22:09 ` 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=57895F16.7010101@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=andrzej.p@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=hans.verkuil@cisco.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=j.anaszewski@samsung.com \
--cc=javier@osg.samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@osg.samsung.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.