From: Max Filippov <jcmvbkbc@gmail.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: "open list:TENSILICA XTENSA PORT (xtensa)"
<linux-xtensa@linux-xtensa.org>, Chris Zankel <chris@zankel.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] xtensa: context tracking updates
Date: Fri, 24 Jun 2022 07:57:09 -0700 [thread overview]
Message-ID: <CAMo8BfLY333gAdztZJa6nm2=mpNyFsBds+d2nRzx6KQ7iWuxsQ@mail.gmail.com> (raw)
In-Reply-To: <20220624140139.GA2050137@lothringen>
On Fri, Jun 24, 2022 at 7:01 AM Frederic Weisbecker <frederic@kernel.org> wrote:
>
> On Sun, Jun 19, 2022 at 04:18:35PM -0700, Max Filippov wrote:
> > Hi Frederic,
> >
> > your recent conversion of CONTEXT_TRACKING to CONTEXT_TRACKING_USER
> > missed the xtensa architexture. These two patches hopefully fix it.
> > Please take them to the tree that holds the rest of the conversion.
> > (Even better if they could be folded into the corresponding conversion
> > patches).
> >
> > Max Filippov (2):
> > xtensa: rename context_tracking_user_{enter,exit}
> > xtensa: rename CONTEXT_TRACKING to CONTEXT_TRACKING_USER
> >
> > arch/xtensa/Kconfig | 2 +-
> > arch/xtensa/kernel/entry.S | 8 ++++----
> > 2 files changed, 5 insertions(+), 5 deletions(-)
> >
> > --
> > Thanks.
> > -- Max
>
> Thanks a lot for these fixes. I'm likely going to reissue this
> patchset so I'm going to fold your changes inside if you don't mind
> (with your Signed-off-by).
Sure, by all means.
--
Thanks.
-- Max
prev parent reply other threads:[~2022-06-24 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 23:18 [PATCH 0/2] xtensa: context tracking updates Max Filippov
2022-06-19 23:18 ` [PATCH 1/2] xtensa: rename context_tracking_user_{enter,exit} Max Filippov
2022-06-19 23:18 ` [PATCH 2/2] xtensa: rename CONTEXT_TRACKING to CONTEXT_TRACKING_USER Max Filippov
2022-06-24 14:01 ` [PATCH 0/2] xtensa: context tracking updates Frederic Weisbecker
2022-06-24 14:57 ` Max Filippov [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='CAMo8BfLY333gAdztZJa6nm2=mpNyFsBds+d2nRzx6KQ7iWuxsQ@mail.gmail.com' \
--to=jcmvbkbc@gmail.com \
--cc=chris@zankel.net \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.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;
as well as URLs for NNTP newsgroup(s).