From: Shuah Khan <skhan@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Beau Belgrave <beaub@linux.microsoft.com>,
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>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 2/2] selftests/user_events: Fix abi_test for BE archs
Date: Wed, 4 Oct 2023 10:38:48 -0600 [thread overview]
Message-ID: <55213463-8834-4ed6-b0a2-1be69dd838d2@linuxfoundation.org> (raw)
In-Reply-To: <20231004111437.47c80c81@gandalf.local.home>
On 10/4/23 09:14, Steven Rostedt wrote:
> On Wed, 4 Oct 2023 09:10:52 -0600
> Shuah Khan <skhan@linuxfoundation.org> wrote:
>
>> On 10/3/23 18:59, Steven Rostedt wrote:
>>>
>>> Note, this doesn't seem to apply to my tree so I only added the first
>>> patch. I think this needs to go through Shuah's tree.
>>>
>>> -- Steve
>>>
>>>
>>
>> Yes. I sent a fix up for rc4 - I can pull these two patches into
>> linux-kselftest next
>>
>> Steve! Does that work for you?
>>
>
> I applied the first patch to my tree, I think the second patch is fine to go
> separately through your tree.
>
Yes I will apply this to linux-kselftest fixes branch once my PR
clears.
thanks,
-- Shuah
next prev parent reply other threads:[~2023-10-04 16:38 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 [this message]
2023-10-05 14:48 ` Shuah Khan
2023-10-05 15:08 ` Steven Rostedt
2023-10-05 16:52 ` Beau Belgrave
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=55213463-8834-4ed6-b0a2-1be69dd838d2@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=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 \
/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®