From: Greg KH <gregkh@linuxfoundation.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] coresight: Patches for v5.12 (part 2)
Date: Wed, 10 Feb 2021 18:11:09 +0100 [thread overview]
Message-ID: <YCQTrSzWH2B/YaVr@kroah.com> (raw)
In-Reply-To: <YCQTineSi2DMPyHs@kroah.com>
On Wed, Feb 10, 2021 at 06:10:34PM +0100, Greg KH wrote:
> On Wed, Feb 10, 2021 at 09:36:08AM -0700, Mathieu Poirier wrote:
> > Hi Greg,
> >
> > Please see if you can add these 2 patches to your 5.12 tally. No worries
> > if you think it is too close to the merge window, I'll simply queue them
> > for the next one.
> >
> > Thanks,
> > Mathieu
> >
> > Leo Yan (1):
> > Documentation: coresight: Add PID tracing description
> >
> > Suzuki K Poulose (1):
> > coresight: etm-perf: Support PID tracing for kernel at EL2
> >
> > Documentation/trace/coresight/coresight.rst | 32 +++++++++++++++++++
> > .../hwtracing/coresight/coresight-etm-perf.c | 27 +++++++++++++++-
> > .../coresight/coresight-etm4x-core.c | 13 ++++++++
> > include/linux/coresight-pmu.h | 3 ++
> > 4 files changed, 74 insertions(+), 1 deletion(-)
>
> This does not apply to my char-misc-next branch (the second patch does
> not apply, I'll take the first one.) Can you fix it up and resend?
Oops, I mean the first one doesn't apply, so I'm not going to take
either.
thanks,
greg k-
prev parent reply other threads:[~2021-02-10 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 16:36 Mathieu Poirier
2021-02-10 16:36 ` [PATCH 1/2] coresight: etm-perf: Support PID tracing for kernel at EL2 Mathieu Poirier
2021-02-10 16:36 ` [PATCH 2/2] Documentation: coresight: Add PID tracing description Mathieu Poirier
2021-02-10 17:10 ` [PATCH 0/2] coresight: Patches for v5.12 (part 2) Greg KH
2021-02-10 17:11 ` Greg KH [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=YCQTrSzWH2B/YaVr@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
/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®