From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Steven Rostedt <rostedt@goodmis•org>,
Masami Hiramatsu <mhiramat@kernel•org>,
Shuah Khan <shuah@kernel•org>
Cc: Beau Belgrave <beaub@linux•microsoft.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Shuah Khan <skhan@linuxfoundation•org>
Subject: linux-next: manual merge of the ftrace tree with the kselftest-fixes tree
Date: Wed, 18 Oct 2023 12:30:14 +1100 [thread overview]
Message-ID: <20231018123014.65073211@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1990 bytes --]
Hi all,
Today's linux-next merge of the ftrace tree got a conflict in:
tools/testing/selftests/user_events/abi_test.c
between commit:
cf5a103c98a6 ("selftests/user_events: Fix abi_test for BE archs")
from the kselftest-fixes tree and commit:
cf74c59c4fc1 ("selftests/user_events: Test persist flag cases")
from the ftrace tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc tools/testing/selftests/user_events/abi_test.c
index f5575ef2007c,3d539e556dcd..000000000000
--- a/tools/testing/selftests/user_events/abi_test.c
+++ b/tools/testing/selftests/user_events/abi_test.c
@@@ -47,7 -59,22 +59,22 @@@ static int change_event(bool enable
return ret;
}
- static int reg_enable(void *enable, int size, int bit)
+ static int event_delete(void)
+ {
+ int fd = open(data_file, O_RDWR);
+ int ret;
+
+ if (fd < 0)
+ return -1;
+
+ ret = ioctl(fd, DIAG_IOCSDEL, "__abi_event");
+
+ close(fd);
+
+ return ret;
+ }
+
-static int reg_enable_flags(long *enable, int size, int bit, int flags)
++static int reg_enable_flags(void *enable, int size, int bit, int flags)
{
struct user_reg reg = {0};
int fd = open(data_file, O_RDWR);
@@@ -69,7 -97,12 +97,12 @@@
return ret;
}
-static int reg_enable(long *enable, int size, int bit)
++static int reg_enable(void *enable, int size, int bit)
+ {
+ return reg_enable_flags(enable, size, bit, 0);
+ }
+
-static int reg_disable(long *enable, int bit)
+static int reg_disable(void *enable, int bit)
{
struct user_unreg reg = {0};
int fd = open(data_file, O_RDWR);
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-10-18 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 1:30 Stephen Rothwell [this message]
2023-10-18 16:01 ` linux-next: manual merge of the ftrace tree with the kselftest-fixes tree Shuah Khan
2023-10-18 16:07 ` Steven Rostedt
2023-10-18 17:54 ` Shuah Khan
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=20231018123014.65073211@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=beaub@linux$(echo .)microsoft.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mhiramat@kernel$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
--cc=shuah@kernel$(echo .)org \
--cc=skhan@linuxfoundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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