From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: mathieu.poirier@linaro.org
Cc: coresight@lists.linaro.org, robin.murphy@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/4] coresight: tmc-etr: Do not call smp_processor_id() from preemptible
Date: Thu, 6 Jun 2019 13:59:50 +0100 [thread overview]
Message-ID: <c4b3ff16-904b-1755-b622-33b2d38bcedf@arm.com> (raw)
In-Reply-To: <20190603192902.GB20462@xps15>
On 03/06/2019 20:29, Mathieu Poirier wrote:
> On Thu, May 30, 2019 at 05:54:24PM +0100, Suzuki K Poulose wrote:
>> Instead of using smp_processor_id() to figure out the node,
>> use the numa_node_id() for the current CPU node to avoid
>> splats like :
>
> I was in the process of applying this set when I noticed the changelogs are
> still referring to numa_node_id(), which is not part of the solution anymore.
> Please address in all 4 patches.
>
Sorry about the last minute messup. I will resend it.
Cheers
Suzuki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-06 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 16:54 [PATCH v3 0/4] coresight: Do not call smp_processor_id from preemptible contexts Suzuki K Poulose
2019-05-30 16:54 ` [PATCH v3 1/4] coresight: tmc-etr: Do not call smp_processor_id() from preemptible Suzuki K Poulose
2019-06-03 19:29 ` Mathieu Poirier
2019-06-06 12:59 ` Suzuki K Poulose [this message]
2019-05-30 16:54 ` [PATCH v3 2/4] coresight: tmc-etr: alloc_perf_buf: Do not call smp_processor_id " Suzuki K Poulose
2019-05-30 16:54 ` [PATCH v3 3/4] coresight: tmc-etf: " Suzuki K Poulose
2019-05-30 16:54 ` [PATCH v3 4/4] coresight: etb10: " Suzuki K Poulose
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=c4b3ff16-904b-1755-b622-33b2d38bcedf@arm.com \
--to=suzuki.poulose@arm.com \
--cc=coresight@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robin.murphy@arm.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