linux-pwm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: Simon South <simon@simonsouth.net>,
	linux-pwm@vger.kernel.org, David Wu <david.wu@rock-chips.com>,
	steven.liu@rock-chips.com
Subject: Re: [PATCH v3 7/7] pwm: rockchip: Enable clock before calling clk_get_rate()
Date: Wed, 13 Jan 2021 10:16:51 +0100	[thread overview]
Message-ID: <20210113091651.u6bylq6i2xeyrmwh@pengutronix.de> (raw)
In-Reply-To: <CAKUh=Rw=9u-hhjRv6cFMLuq0+od=gAGedbv-on1rgGweWu_SeA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 489 bytes --]

Hi Kever,

[stripped recipients a bit]

On Fri, Dec 25, 2020 at 03:15:12PM +0800, Kever Yang wrote:
> + David and Steven,
> 
> Hi Steven,
>     please help to review this patch set.

I wonder if a private message would have been enough instead of seven
identical mails to a massive set of people.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-01-13  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-25  7:15 [PATCH v3 7/7] pwm: rockchip: Enable clock before calling clk_get_rate() Kever Yang
2021-01-13  9:16 ` Uwe Kleine-König [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-23 16:01 [PATCH v3 0/7] pwm: rockchip: Eliminate potential race condition when probing Simon South
2020-12-23 16:01 ` [PATCH v3 7/7] pwm: rockchip: Enable clock before calling clk_get_rate() Simon South
2021-01-13  7:54   ` Uwe Kleine-König

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=20210113091651.u6bylq6i2xeyrmwh@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=david.wu@rock-chips.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-pwm@vger.kernel.org \
    --cc=simon@simonsouth.net \
    --cc=steven.liu@rock-chips.com \
    /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).