From: Mark Brown <broonie@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the kspp tree with the origin tree
Date: Tue, 10 Feb 2026 21:08:22 +0000 [thread overview]
Message-ID: <aYueRmtXzWX5UGf2@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2699 bytes --]
Hi all,
Today's linux-next merge of the kspp tree got a conflict in:
scripts/coccinelle/api/kmalloc_objs.cocci
between commit:
bdc5071d7f7bb ("coccinelle: Add kmalloc_objs conversion script")
from the origin tree and commit:
52d3cfa9bfcd4 ("coccinelle: Add kmalloc_objs conversion script")
from the kspp 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.
diff --combined scripts/coccinelle/api/kmalloc_objs.cocci
index db12b7be7247a,916cc3a661b97..0000000000000
--- a/scripts/coccinelle/api/kmalloc_objs.cocci
+++ b/scripts/coccinelle/api/kmalloc_objs.cocci
@@@ -33,18 -33,15 +33,18 @@@ def alloc_array(name)
typedef u8, u16, u32, u64;
typedef __u8, __u16, __u32, __u64;
typedef uint8_t, uint16_t, uint32_t, uint64_t;
+typedef uchar, ushort, uint, ulong;
typedef __le16, __le32, __le64;
typedef __be16, __be32, __be64;
-type INTEGRAL = {u8,__u8,uint8_t,char,unsigned char,
- u16,__u16,uint16_t,unsigned short,
- u32,__u32,uint32_t,unsigned int,
- u64,__u64,uint64_t,unsigned long,
+typedef wchar_t;
+type INTEGRAL = {u8,__u8,uint8_t,char,unsigned char,uchar,wchar_t,
+ u16,__u16,uint16_t,unsigned short,ushort,
+ u32,__u32,uint32_t,unsigned int,uint,
+ u64,__u64,uint64_t,unsigned long,ulong,
__le16,__le32,__le64,__be16,__be32,__be64};
char [] STRING;
INTEGRAL *BYTES;
+INTEGRAL **BYTES_PTRS;
type TYPE;
expression VAR;
expression GFP;
@@@ -67,10 -64,6 +67,10 @@@ fresh identifier ALLOC_OBJS = script:py
BYTES = ALLOC((sizeof(E)), GFP)
|
BYTES = ALLOC((sizeof(TYPE)), GFP)
+|
+ BYTES_PTRS = ALLOC((sizeof(E)), GFP)
+|
+ BYTES_PTRS = ALLOC((sizeof(TYPE)), GFP)
|
ALLOC((sizeof(void *)), GFP)
|
@@@ -85,20 -78,12 +85,20 @@@
BYTES = ALLOC_ARRAY(COUNT, (sizeof(E)), GFP)
|
BYTES = ALLOC_ARRAY(COUNT, (sizeof(TYPE)), GFP)
+|
+ BYTES_PTRS = ALLOC_ARRAY(COUNT, (sizeof(E)), GFP)
+|
+ BYTES_PTRS = ALLOC_ARRAY(COUNT, (sizeof(TYPE)), GFP)
|
ALLOC_ARRAY((\(sizeof(STRING)\|sizeof(INTEGRAL)\|sizeof(INTEGRAL *)\)), COUNT, GFP)
|
BYTES = ALLOC_ARRAY((sizeof(E)), COUNT, GFP)
|
BYTES = ALLOC_ARRAY((sizeof(TYPE)), COUNT, GFP)
+|
+ BYTES_PTRS = ALLOC_ARRAY((sizeof(E)), COUNT, GFP)
+|
+ BYTES_PTRS = ALLOC_ARRAY((sizeof(TYPE)), COUNT, GFP)
|
ALLOC_ARRAY(COUNT, (sizeof(void *)), GFP)
|
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-02-10 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 21:08 Mark Brown [this message]
2026-02-10 23:43 ` linux-next: manual merge of the kspp tree with the origin tree Kees Cook
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=aYueRmtXzWX5UGf2@sirena.org.uk \
--to=broonie@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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