From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Yabin Cui <yabinc@google.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: Re: [PATCH v3] coresight: Serialize enabling/disabling a link device.
Date: Wed, 14 Aug 2019 09:04:22 -0600 [thread overview]
Message-ID: <CANLsYkyjQ2SfA6_1+FVLPwK1V9iqU31vBwHYK4BGewV5o27G7g@mail.gmail.com> (raw)
In-Reply-To: <20190814003557.97004-1-yabinc@google.com>
On Tue, 13 Aug 2019 at 18:36, Yabin Cui <yabinc@google.com> wrote:
>
> > The patch isn't difficult to do but does go deeper in each link
> > drivers (ETF, funnel, replicator). Let me know if you are not
> > comfortable with the idea and I will see what I can do on my side.
>
> I am comfortable with the idea. I chose to add lock in coresight_enable_link() just because it
> is the smallest change. But a refactor probably is better for maintainance.
Yes, that is my prime concern.
>
> Feel free to upload a new patch fixing the problem. I can help to test it.
I have a few things on my plate at this time so you might beat me to
the punch. I'll see how the next few days go.
Mathieu
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-08-14 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 19:57 [PATCH v3] coresight: Serialize enabling/disabling a link device Yabin Cui
2019-08-13 21:30 ` Mathieu Poirier
2019-08-14 0:35 ` Yabin Cui
2019-08-14 15:04 ` Mathieu Poirier [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=CANLsYkyjQ2SfA6_1+FVLPwK1V9iqU31vBwHYK4BGewV5o27G7g@mail.gmail.com \
--to=mathieu.poirier@linaro.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=yabinc@google.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).