public inbox for linux-pwm@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: "Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Lee Jones" <lee.jones@linaro.org>,
	"Guru Das Srinagesh" <gurus@codeaurora.org>,
	linux-pwm@vger.kernel.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] pwm: Miscellaneous fixes for 64-bit support
Date: Mon, 15 Jun 2020 16:16:04 +0200	[thread overview]
Message-ID: <20200615141606.2814208-1-thierry.reding@gmail.com> (raw)

Hi,

this contains a couple of fixes for issues that I ran into after
applying Guru's series to convert PWM period and duty-cycle to 64-bit.

Bartlomiej, can you provide an Acked-by on the first patch so that I can
take it through the PWM tree along with the rest of Guru's series?

Thanks,
Thierry

Thierry Reding (2):
  video: ssd1307fb: Print PWM period using 64-bit format specifier
  pwm: iqs620a: Use 64-bit division

 drivers/pwm/pwm-iqs620a.c       | 7 ++++---
 drivers/video/fbdev/ssd1307fb.c | 2 +-
 2 files changed, 5 insertions(+), 4 deletions(-)

-- 
2.24.1

             reply	other threads:[~2020-06-15 14:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 14:16 Thierry Reding [this message]
2020-06-15 14:16 ` [PATCH 1/2] video: ssd1307fb: Print PWM period using 64-bit format specifier Thierry Reding
2020-06-15 15:18   ` Uwe Kleine-König
2020-06-15 17:19   ` kernel test robot
2020-06-15 17:25   ` kernel test robot
2020-06-17  7:18   ` Geert Uytterhoeven
2020-06-17 17:30     ` Uwe Kleine-König
2020-06-18 20:05     ` Guru Das Srinagesh
2020-06-19  6:46       ` Geert Uytterhoeven
2020-06-15 14:16 ` [PATCH 2/2] pwm: iqs620a: Use 64-bit division Thierry Reding
2020-06-15 15:16   ` Uwe Kleine-König
2020-06-16  7:06   ` Lee Jones

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=20200615141606.2814208-1-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=gurus@codeaurora.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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