From: Guru Das Srinagesh <gurus@codeaurora.org>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: linux-pwm@vger.kernel.org, linux-fbdev@vger.kernel.org,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Thierry Reding" <thierry.reding@gmail.com>,
"Subbaraman Narayanamurthy" <subbaram@codeaurora.org>,
"Lee Jones" <lee.jones@linaro.org>
Subject: Re: [PATCH v7 12/13] backlight: pwm_bl: Use 64-bit division macros for period and duty cycle
Date: Tue, 10 Mar 2020 18:12:42 +0000 [thread overview]
Message-ID: <20200310181242.GA31738@codeaurora.org> (raw)
In-Reply-To: <20200310143432.cfjlqac5x6oinshj@holly.lan>
On Tue, Mar 10, 2020 at 02:34:32PM +0000, Daniel Thompson wrote:
> This patch looks like it is a tiny change to get the pwm_backlight to
> perform 64-bit division. Most of the above text is completely irrelevant
> to the change contained in this patch. No need to justify the change in
> the PWM structures here since that can go in the patch that changes
> those structures. Just describe what this patch does, perhaps something
> like the following:
>
> The PWM API will shortly switch the state.period and
> state.duty_cycle fields to 64-bit values. Make pwm_bl
> ready for this transition by adopting 64-bit division
> macros.
Will update the commit text accordingly.
> Also please copy the backlight maintainers into the covering letter. It
> is useful to place patches like this into context.
Will do.
Thank you.
Guru Das.
prev parent reply other threads:[~2020-03-10 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1583782035.git.gurus@codeaurora.org>
2020-03-09 19:35 ` [PATCH v7 12/13] backlight: pwm_bl: Use 64-bit division macros for period and duty cycle Guru Das Srinagesh
2020-03-10 14:34 ` Daniel Thompson
2020-03-10 18:12 ` Guru Das Srinagesh [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=20200310181242.GA31738@codeaurora.org \
--to=gurus@codeaurora.org \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.thompson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=subbaram@codeaurora.org \
--cc=thierry.reding@gmail.com \
--cc=uwe@kleine-koenig.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;
as well as URLs for NNTP newsgroup(s).