From: tanmay@codeaurora.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
sam@ravnborg.org, seanpaul@chromium.org,
freedreno@lists.freedesktop.org, chandanu@codeaurora.org,
robdclark@gmail.com, abhinavk@codeaurora.org,
nganji@codeaurora.org, linux-clk@vger.kernel.org,
Vara Reddy <varar@codeaurora.org>
Subject: Re: [PATCH v6 2/5] drm: add constant N value in helper file
Date: Thu, 11 Jun 2020 13:07:25 -0700 [thread overview]
Message-ID: <8b8d06e7331a0b8cbe3e674864c16f0c@codeaurora.org> (raw)
In-Reply-To: <159175565407.242598.7527036274929582020@swboyd.mtv.corp.google.com>
On 2020-06-09 19:20, Stephen Boyd wrote:
> Quoting Tanmay Shah (2020-06-08 20:40:47)
>> From: Chandan Uddaraju <chandanu@codeaurora.org>
>>
>> The constant N value (0x8000) is used by i915 DP
>> driver. Define this value in dp helper header file
>> to use in multiple Display Port drivers. Change
>> i915 driver accordingly.
>>
>> Change in v6: Change commit message
>>
>> Signed-off-by: Chandan Uddaraju <chandanu@codeaurora.org>
>> Signed-off-by: Vara Reddy <varar@codeaurora.org>
>> Signed-off-by: Tanmay Shah <tanmay@codeaurora.org>
>> ---
>
> Reviewed-by: Stephen Boyd <swboyd@chromium.org>
>
> Can you resend this series as an actual patch series? None of the
> patches have the proper In-Reply-To headers so it is hard to track the
> thread.
Sure. Should I keep Message-ID of v5-patch-1 for in-reply-to header?
next prev parent reply other threads:[~2020-06-11 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 3:40 [PATCH v6 2/5] drm: add constant N value in helper file Tanmay Shah
2020-06-10 2:20 ` Stephen Boyd
2020-06-11 20:07 ` tanmay [this message]
2020-06-11 9:25 ` Jani Nikula
-- strict thread matches above, loose matches on Subject: below --
2020-06-12 1:50 [PATCH v6 0/5] Add support for DisplayPort driver on Tanmay Shah
2020-06-12 1:50 ` [PATCH v6 2/5] drm: add constant N value in helper file Tanmay Shah
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=8b8d06e7331a0b8cbe3e674864c16f0c@codeaurora.org \
--to=tanmay@codeaurora.org \
--cc=abhinavk@codeaurora.org \
--cc=chandanu@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=nganji@codeaurora.org \
--cc=robdclark@gmail.com \
--cc=sam@ravnborg.org \
--cc=seanpaul@chromium.org \
--cc=swboyd@chromium.org \
--cc=varar@codeaurora.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