Linux-Tegra Archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>,
	thierry.reding@gmail.com, jonathanh@nvidia.com,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH v3 0/7] Cleanup Tegra210 EMC frequency scaling
Date: Mon, 6 May 2024 10:07:13 +0200	[thread overview]
Message-ID: <33a90ca9-86f6-4d17-8775-54b2ce83a2f3@linaro.org> (raw)
In-Reply-To: <20240429101933.11500-1-diogo.ivo@tecnico.ulisboa.pt>

On 29/04/2024 12:19, Diogo Ivo wrote:
> Hello,
> 
> This patch series consists of a general cleanup of the Tegra210 EMC
> frequency scaling code for revision 7.
> 
> Currently the code is relying heavily on a function, update_clock_tree_delay(),
> that is responsible for too many things, making it long and confusing.
> The general idea with these patches is to simplify this function and its
> surrounding code, making it more modular.

One more thing:
Your v2 was not build tested by you, was missed by LKP and you did not
Cc kernel mailing list. Maybe LKP missed it because you reduced the
recipients list, which is surprising. I do not see any reason why
removing output of get_maintainers for this patch.

Therefore anyway please resend including ALL mailing lists and ALL
maintainers, so I can have some confidence that LKP picked this up.

Best regards,
Krzysztof


      parent reply	other threads:[~2024-05-06  8:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 10:19 [PATCH v3 0/7] Cleanup Tegra210 EMC frequency scaling Diogo Ivo
2024-04-29 10:19 ` [PATCH v3 1/7] memory: tegra: Remove periodic compensation duplicate calls Diogo Ivo
2024-04-29 10:19 ` [PATCH v3 2/7] memory: tegra: Move DQSOSC measurement to common place Diogo Ivo
2024-04-29 10:19 ` [PATCH v3 3/7] memory: tegra: Reword and correct comments Diogo Ivo
2024-04-29 10:19 ` [PATCH v3 4/7] memory: tegra: Change macros to interpret parameter as integer Diogo Ivo
2024-04-29 10:19 ` [PATCH v3 5/7] memory: tegra: Loop update_clock_tree_delay() Diogo Ivo
2024-04-29 10:19 ` [PATCH v3 6/7] memory: tegra: Move compare/update current delay values to a function Diogo Ivo
2024-04-29 10:19 ` [PATCH v3 7/7] memory: tegra: Rework update_clock_tree_delay() Diogo Ivo
2024-05-04 12:20 ` [PATCH v3 0/7] Cleanup Tegra210 EMC frequency scaling Krzysztof Kozlowski
2024-05-06  8:07 ` Krzysztof Kozlowski [this message]

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=33a90ca9-86f6-4d17-8775-54b2ce83a2f3@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=diogo.ivo@tecnico.ulisboa.pt \
    --cc=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).