From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Alim Akhtar <alim.akhtar@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: linux-samsung-soc@vger.kernel.org, daniel.lezcano@linaro.org,
tglx@linutronix.de, pankaj.dubey@samsung.com,
m.szyprowski@samsung.com
Subject: Re: [PATCH v2 1/3] clocksource/drivers/exynos_mct: Remove mct interrupt index enum
Date: Sun, 20 Feb 2022 16:30:26 +0100 [thread overview]
Message-ID: <289ebc45-4070-920c-cba7-fa7120d2bf4a@canonical.com> (raw)
In-Reply-To: <20220220133824.33837-1-alim.akhtar@samsung.com>
On 20/02/2022 14:38, Alim Akhtar wrote:
> MCT driver define an enum which list global and local timer's
> irq index. Most of them are not used but MCT_G0_IRQ and
> MCT_L0_IRQ and these two are at a fixed offset/index.
> Get rid of this enum and use a #define for the used irq index.
>
> No functional changes expected.
>
> Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
> ---
> drivers/clocksource/exynos_mct.c | 22 ++++++----------------
> 1 file changed, 6 insertions(+), 16 deletions(-)
>
> * Changes since v1:
> - Seperate out bumping up of max mct irq and local timer number
> as commented by Krzysztof
>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Best regards,
Krzysztof
prev parent reply other threads:[~2022-02-20 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220220132636epcas5p4f320ac6dff9621b75481bd71b1f33183@epcas5p4.samsung.com>
2022-02-20 13:38 ` Alim Akhtar
[not found] ` <CGME20220220132640epcas5p1a523e6db151e0cb76c0edb6d32959fe5@epcas5p1.samsung.com>
2022-02-20 13:38 ` [PATCH v2 2/3] clocksource/drivers/exynos_mct: bump up mct max irq number Alim Akhtar
2022-02-20 15:32 ` Krzysztof Kozlowski
[not found] ` <CGME20220220132643epcas5p39d48a27bb3fcde2ea3a01a260b46e1a0@epcas5p3.samsung.com>
2022-02-20 13:38 ` [PATCH v2 3/3] clocksource/drivers/exynos_mct: bump up number of local timer Alim Akhtar
2022-02-20 15:33 ` Krzysztof Kozlowski
2022-02-20 16:59 ` Alim Akhtar
2022-02-20 17:34 ` Krzysztof Kozlowski
2022-02-20 15:30 ` 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=289ebc45-4070-920c-cba7-fa7120d2bf4a@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=alim.akhtar@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=pankaj.dubey@samsung.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®