Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Crystal Guo <crystal.guo@mediatek.com>,
	Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	Project_Global_Chrome_Upstream_Group@mediatek.com,
	kernel test robot <lkp@intel.com>
Subject: Re: [v2,1/2] memory/mediatek: Add an interface to get current DDR data rate
Date: Sun, 9 Feb 2025 11:50:12 +0100	[thread overview]
Message-ID: <eac3c588-0c9a-4bd6-8ef2-e05eec6c377a@kernel.org> (raw)
In-Reply-To: <20250207014437.17920-2-crystal.guo@mediatek.com>

On 07/02/2025 02:42, Crystal Guo wrote:
> Add MediaTek DRAMC driver to provide an interface that can
> obtain current DDR data rate.
> 
> Reported-by: kernel test robot <lkp@intel.com>

Kbuild did not report here anything.

> Closes: https://lore.kernel.org/oe-kbuild-all/202412210955.FvO0Pee3-lkp@intel.
> com/
> Signed-off-by: Crystal Guo <crystal.guo@mediatek.com>
> ---
>  drivers/memory/Kconfig              |   1 +
>  drivers/memory/Makefile             |   1 +
>  drivers/memory/mediatek/Kconfig     |  21 +++
>  drivers/memory/mediatek/Makefile    |   2 +
>  drivers/memory/mediatek/mtk-dramc.c | 196 ++++++++++++++++++++++++++++
>  5 files changed, 221 insertions(+)
>  create mode 100644 drivers/memory/mediatek/Kconfig
>  create mode 100644 drivers/memory/mediatek/Makefile
>  create mode 100644 drivers/memory/mediatek/mtk-dramc.c


You sent same patchsets multiple times.

Before next posting, please really carefully go through the guides and
process.

Best regards,
Krzysztof


  reply	other threads:[~2025-02-09 10:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07  1:42 [v2,0/2] Add an interface to get current DDR data rate Crystal Guo
2025-02-07  1:42 ` [v2,1/2] memory/mediatek: " Crystal Guo
2025-02-09 10:50   ` Krzysztof Kozlowski [this message]
2025-02-11 11:33     ` Crystal Guo (郭晶)
2025-03-04 14:59   ` AngeloGioacchino Del Regno
2025-03-17  2:30     ` Crystal Guo (郭晶)
2025-02-07  1:42 ` [v2,2/2] dt-bindings: memory-controllers: Add MediaTek DRAM controller interface Crystal Guo
2025-02-09 10:51   ` Krzysztof Kozlowski
2025-02-12  3:50     ` Crystal Guo (郭晶)
2025-02-12  5:34       ` Krzysztof Kozlowski
2025-02-12 10:07         ` Crystal Guo (郭晶)
  -- strict thread matches above, loose matches on Subject: below --
2025-02-06 12:16 [v2,0/2] Add an interface to get current DDR data rate Crystal Guo
2025-02-06 12:16 ` [v2,1/2] memory/mediatek: " Crystal Guo
2025-02-06 12:31   ` AngeloGioacchino Del Regno
2025-02-07  1:30     ` Crystal Guo (郭晶)
2025-02-09 10:51   ` Krzysztof Kozlowski

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=eac3c588-0c9a-4bd6-8ef2-e05eec6c377a@kernel.org \
    --to=krzk@kernel.org \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=crystal.guo@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=lkp@intel.com \
    --cc=matthias.bgg@gmail.com \
    --cc=robh@kernel.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