From: Greg KH <gregkh@linuxfoundation.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org,
mike.leach@linaro.org, james.clark@arm.com,
anshuman.khandual@arm.com, leo.yan@linaro.org,
scclevenger@os.amperecomputing.com
Subject: Re: [GIT PULL] coresight: Fixes for v6.3
Date: Wed, 5 Apr 2023 12:31:04 +0200 [thread overview]
Message-ID: <2023040500-apron-sandfish-af52@gregkh> (raw)
In-Reply-To: <c5fce990-bf13-4cc9-6451-f44fff1176d7@arm.com>
On Wed, Apr 05, 2023 at 11:16:17AM +0100, Suzuki K Poulose wrote:
> Hi Greg,
>
> On 21/03/2023 16:21, Greg KH wrote:
> > On Tue, Mar 21, 2023 at 01:38:52PM +0000, Suzuki K Poulose wrote:
> > > Greg,
> > >
> > > Please find a couple of fixes for coresight self-hosted tracing for v6.3. Kindly
> > > consider pulling.
> > >
> > > Suzuki
> > >
> > >
> > > The following changes since commit eeac8ede17557680855031c6f305ece2378af326:
> > >
> > > Linux 6.3-rc2 (2023-03-12 16:36:44 -0700)
> > >
> > > are available in the Git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/coresight/linux.git tags/coresight-fixes-v6.3
>
> >
> > Pulled and pushed out, thanks.
>
> Just wondering, why this hasn't shown up on linus' tree yet ? Do you plan to
> send it for rc6 ?
Yes.
_______________________________________________
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:[~2023-04-05 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 13:38 [GIT PULL] coresight: Fixes for v6.3 Suzuki K Poulose
2023-03-21 16:21 ` Greg KH
2023-04-05 10:16 ` Suzuki K Poulose
2023-04-05 10:31 ` Greg KH [this message]
2023-04-05 10:32 ` 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=2023040500-apron-sandfish-af52@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=anshuman.khandual@arm.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mike.leach@linaro.org \
--cc=scclevenger@os.amperecomputing.com \
--cc=suzuki.poulose@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