All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] mmc: sh_mmcif: Use "kHz" for kilohertz
Date: Mon, 6 Jul 2020 16:48:48 +0200	[thread overview]
Message-ID: <CAPDyKFq2BV72hqqW0P0d+=+8Hy4oONhYc2gAf7U9nCvUfYxedA@mail.gmail.com> (raw)
In-Reply-To: <20200618080321.16678-1-geert+renesas@glider.be>

On Thu, 18 Jun 2020 at 10:03, Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
>
> "K" stands for "kelvin".
>
> While at it, make the spacing before units consistent.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

Applied for next, thanks!

Kind regards
Uffe


> ---
>  drivers/mmc/host/sh_mmcif.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mmc/host/sh_mmcif.c b/drivers/mmc/host/sh_mmcif.c
> index 7e1fd557109c0476..9f53634aa41184c8 100644
> --- a/drivers/mmc/host/sh_mmcif.c
> +++ b/drivers/mmc/host/sh_mmcif.c
> @@ -191,9 +191,9 @@
>                                  STS2_AC12BSYTO | STS2_RSPBSYTO |       \
>                                  STS2_AC12RSPTO | STS2_RSPTO)
>
> -#define CLKDEV_EMMC_DATA       52000000 /* 52MHz */
> -#define CLKDEV_MMC_DATA                20000000 /* 20MHz */
> -#define CLKDEV_INIT            400000   /* 400 KHz */
> +#define CLKDEV_EMMC_DATA       52000000 /* 52 MHz */
> +#define CLKDEV_MMC_DATA                20000000 /* 20 MHz */
> +#define CLKDEV_INIT            400000   /* 400 kHz */
>
>  enum sh_mmcif_state {
>         STATE_IDLE,
> --
> 2.17.1
>

  reply	other threads:[~2020-07-06 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18  8:03 [PATCH] mmc: sh_mmcif: Use "kHz" for kilohertz Geert Uytterhoeven
2020-07-06 14:48 ` Ulf Hansson [this message]
2020-07-06 14:50 ` Wolfram Sang

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='CAPDyKFq2BV72hqqW0P0d+=+8Hy4oONhYc2gAf7U9nCvUfYxedA@mail.gmail.com' \
    --to=ulf.hansson@linaro.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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 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.