From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Youngmin Nam <youngmin.nam@samsung.com>,
Sam Protsenko <semen.protsenko@linaro.org>
Cc: tomasz.figa@gmail.com, s.nawrocki@samsung.com,
alim.akhtar@samsung.com, linus.walleij@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] pinctrl: samsung: add irq_set_affinity() for non wake up external gpio interrupt
Date: Thu, 30 Nov 2023 08:56:15 +0100 [thread overview]
Message-ID: <e90e171f-8fd9-4b93-9d9c-7216448ca6d0@linaro.org> (raw)
In-Reply-To: <ZWg5/rorgfSM/5UO@perf>
On 30/11/2023 08:30, Youngmin Nam wrote:
> Thanks for your test Sam. It's really great work.
> I confirmed the patch did work by following your test sequence as below.
>
> * Before
> CPU0 CPU1 CPU2 CPU3 CPU4 ...
> 87: 40 0 0 0 0 ... gpg1 0 Edge Test Key
>
> * After
> 87: 40 0 0 0 22 ... gpg1 0 Edge Test Key
>
> Krzysztof,
> Sam and I tested this patch on e850-95 board.
> Let me update commit message with test result and will update patchset.
Be sure you always run checkpatch on every patch you send.
[Checkpatch]
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit
description?)
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-30 7:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231126091120epcas2p4a1320e3b0f9be8f8a0f575a322981d38@epcas2p4.samsung.com>
2023-11-26 9:46 ` [PATCH v2] pinctrl: samsung: add irq_set_affinity() for non wake up external gpio interrupt Youngmin Nam
2023-11-27 9:54 ` Krzysztof Kozlowski
2023-11-28 1:01 ` Youngmin Nam
2023-11-28 7:29 ` Krzysztof Kozlowski
2023-11-28 21:35 ` Sam Protsenko
2023-11-29 7:07 ` Youngmin Nam
2023-11-29 8:00 ` Krzysztof Kozlowski
2023-11-29 8:46 ` Youngmin Nam
2023-11-29 8:39 ` Krzysztof Kozlowski
2023-11-29 10:04 ` Youngmin Nam
2023-11-29 18:48 ` Sam Protsenko
2023-11-30 7:30 ` Youngmin Nam
2023-11-30 7:56 ` Krzysztof Kozlowski [this message]
2023-11-30 7:55 ` 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=e90e171f-8fd9-4b93-9d9c-7216448ca6d0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=semen.protsenko@linaro.org \
--cc=tomasz.figa@gmail.com \
--cc=youngmin.nam@samsung.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 NNTP newsgroup(s).