All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Dongjin Kim <tobetter@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Kevin Hilman <khilman@baylibre.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: meson-sm1: fix typo in opp table
Date: Sat, 5 Dec 2020 13:00:35 +0100	[thread overview]
Message-ID: <CAFBinCA=A+M0dgebTRF3y6chd205HN5ORgqBxw1gpu++7QC8Rw@mail.gmail.com> (raw)
In-Reply-To: <20201130060320.GA30098@anyang-linuxfactory-or-kr>

On Mon, Nov 30, 2020 at 7:04 AM Dongjin Kim <tobetter@gmail.com> wrote:
>
> The freqency 1512000000 should be 1500000000.
there's a typo in "frequency". I hope that Kevin can fix this up while
applying the patch

>
> Signed-off-by: Dongjin Kim <tobetter@gmail.com>
apart from the typo above:
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
(while reviewing I noticed that we generally use 0.3V less for each
OPP table step than the downstream kvim3l.dts - that's a discussion we
need to have elsewhere though)

WARNING: multiple messages have this Message-ID (diff)
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Dongjin Kim <tobetter@gmail.com>
Cc: devicetree@vger.kernel.org, Kevin Hilman <khilman@baylibre.com>,
	linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: dts: meson-sm1: fix typo in opp table
Date: Sat, 5 Dec 2020 13:00:35 +0100	[thread overview]
Message-ID: <CAFBinCA=A+M0dgebTRF3y6chd205HN5ORgqBxw1gpu++7QC8Rw@mail.gmail.com> (raw)
In-Reply-To: <20201130060320.GA30098@anyang-linuxfactory-or-kr>

On Mon, Nov 30, 2020 at 7:04 AM Dongjin Kim <tobetter@gmail.com> wrote:
>
> The freqency 1512000000 should be 1500000000.
there's a typo in "frequency". I hope that Kevin can fix this up while
applying the patch

>
> Signed-off-by: Dongjin Kim <tobetter@gmail.com>
apart from the typo above:
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
(while reviewing I noticed that we generally use 0.3V less for each
OPP table step than the downstream kvim3l.dts - that's a discussion we
need to have elsewhere though)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Dongjin Kim <tobetter@gmail.com>
Cc: devicetree@vger.kernel.org, Kevin Hilman <khilman@baylibre.com>,
	linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: dts: meson-sm1: fix typo in opp table
Date: Sat, 5 Dec 2020 13:00:35 +0100	[thread overview]
Message-ID: <CAFBinCA=A+M0dgebTRF3y6chd205HN5ORgqBxw1gpu++7QC8Rw@mail.gmail.com> (raw)
In-Reply-To: <20201130060320.GA30098@anyang-linuxfactory-or-kr>

On Mon, Nov 30, 2020 at 7:04 AM Dongjin Kim <tobetter@gmail.com> wrote:
>
> The freqency 1512000000 should be 1500000000.
there's a typo in "frequency". I hope that Kevin can fix this up while
applying the patch

>
> Signed-off-by: Dongjin Kim <tobetter@gmail.com>
apart from the typo above:
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
(while reviewing I noticed that we generally use 0.3V less for each
OPP table step than the downstream kvim3l.dts - that's a discussion we
need to have elsewhere though)

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  parent reply	other threads:[~2020-12-05 18:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30  6:03 [PATCH v2] arm64: dts: meson-sm1: fix typo in opp table Dongjin Kim
2020-11-30  6:03 ` Dongjin Kim
2020-11-30  6:03 ` Dongjin Kim
2020-11-30 13:23 ` Neil Armstrong
2020-11-30 13:23   ` Neil Armstrong
2020-11-30 13:23   ` Neil Armstrong
2020-12-05 12:00 ` Martin Blumenstingl [this message]
2020-12-05 12:00   ` Martin Blumenstingl
2020-12-05 12:00   ` Martin Blumenstingl

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='CAFBinCA=A+M0dgebTRF3y6chd205HN5ORgqBxw1gpu++7QC8Rw@mail.gmail.com' \
    --to=martin.blumenstingl@googlemail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tobetter@gmail.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.