From: Beau Belgrave <beaub@linux.microsoft.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
mhiramat@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, cleger@rivosinc.com,
linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 2/2] selftests/user_events: Fix abi_test for BE archs
Date: Thu, 5 Oct 2023 09:52:30 -0700 [thread overview]
Message-ID: <20231005165230.GA1247-beaub@linux.microsoft.com> (raw)
In-Reply-To: <20231005110816.4b68453d@gandalf.local.home>
On Thu, Oct 05, 2023 at 11:08:15AM -0400, Steven Rostedt wrote:
> On Thu, 5 Oct 2023 08:48:14 -0600
> Shuah Khan <skhan@linuxfoundation.org> wrote:
>
> > Hmm. Which tree is this patch based on? This doesn't apply to
> > linux-kselftest fixes - I thought this was based on top of fixes
> > since I sent in a fix for Linux 6.6-rc4 for user_events
> >
> > Beau, Please rebase to the correct tree/branch and send v2 for
> > this patch.
>
> Hmm, so this didn't apply to my tree nor yours.
>
> Beau, can you verify which tree this goes to?
>
> -- Steve
It was based on tracing/for-next.
I'll get a v2 out rebased upon linux-kselftest, does that work?
Thanks,
-Beau
next prev parent reply other threads:[~2023-10-05 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 23:08 [PATCH 0/2] tracing/user_events: Fix alignment issues for 32 on 64-bit and BE Beau Belgrave
2023-09-25 23:08 ` [PATCH 1/2] tracing/user_events: Align set_bit() address for all archs Beau Belgrave
2023-09-25 23:08 ` [PATCH 2/2] selftests/user_events: Fix abi_test for BE archs Beau Belgrave
2023-10-04 0:59 ` Steven Rostedt
2023-10-04 15:10 ` Shuah Khan
2023-10-04 15:14 ` Steven Rostedt
2023-10-04 16:38 ` Shuah Khan
2023-10-05 14:48 ` Shuah Khan
2023-10-05 15:08 ` Steven Rostedt
2023-10-05 16:52 ` Beau Belgrave [this message]
2023-10-05 17:46 ` Steven Rostedt
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=20231005165230.GA1247-beaub@linux.microsoft.com \
--to=beaub@linux.microsoft.com \
--cc=cleger@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.