From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wr1-f48.google.com (mail-wr1-f48.google.com [209.85.221.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2E5EF343D80 for ; Thu, 16 Jul 2026 10:14:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.221.48 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784196847; cv=none; b=i/dxBv5fQ8diPxvVi9wHNVepghPUxpANjp02/SUD2xlfzAh8D2iVIAK+iZXcdZ6Nuw0j8QnC4dwlAVlIon/8T78kdRhkPiPobMPndmTJtN5VhcAu3Qk/nUcq1ogDwA7CfWRH+BPKKf6IYvlybbq0uEdUcIbhy7jjCjmNYAUGRlY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784196847; c=relaxed/simple; bh=0/tBC0KCUh5LW7IzaPJv9dSEedswCYxIQ3e8GciJMQc=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ujhY23OrsbhlshWE5YuQc4p6e9c5pVCDh6yv5P5MUIU3f1XwaLyLUD18K2fhkhsgI1Lyw6wCFP+GiCXm6hMadhRJ5qxERfpGhiYTAdC419evVhpalwjXRfs89BXOHTUyBwSWTOlP6yGJgQUC0F70HfbEyeAjOrAPgBCZhcSai40= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=baylibre.com; spf=pass smtp.mailfrom=baylibre.com; dkim=pass (2048-bit key) header.d=baylibre.com header.i=@baylibre.com header.b=QX+HBYUP; arc=none smtp.client-ip=209.85.221.48 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=baylibre.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=baylibre.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=baylibre.com header.i=@baylibre.com header.b="QX+HBYUP" Received: by mail-wr1-f48.google.com with SMTP id ffacd0b85a97d-475881b9a4bso2878650f8f.3 for ; Thu, 16 Jul 2026 03:14:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre.com; s=google; t=1784196841; x=1784801641; darn=vger.kernel.org; h=in-reply-to:content-disposition:content-type:mime-version :references:message-id:subject:cc:to:from:date:from:to:cc:subject :date:message-id:reply-to:content-type; bh=UdByQpacz1nyXIEUp0L36KxSugQAT44TfZyhzwyhKm0=; b=QX+HBYUPF+7SP3XCV4gKncPTuq6Tnl153VewXS6ZzlhKGQsDa2K+0SG/9Xp0/vsaxF gNcp+It+Fgad+TmZCmFpldBZot5dOxTCBZ9u1psR0xVjxpnfn7bCUQxV6I3lVwyXXcjL i4UM0+ejC2i205uXZPjpk6Bm1G8n3palH3Tze7l4ENi+Qj6cw3wxw8xucfKpuekN1H+v 30+r7J+IDrm24YWZWdRZTxXHcFYoy8fc8E6+l6vNAjWdkv8hPKd9+8hqcIgRQ9dm+Rng n3F45rlXsslkuLyNW69kvUB0ON3rgV6yTvHzdie2J4vxVu9j3HfiQFDDsX/4MvKGr55h LJGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1784196841; x=1784801641; h=in-reply-to:content-disposition:content-type:mime-version :references:message-id:subject:cc:to:from:date:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=UdByQpacz1nyXIEUp0L36KxSugQAT44TfZyhzwyhKm0=; b=Zj94ZFYDshQrv3pk9IEUGACxuMY41z5yMoEQpUexZEPT6ScEwmCpvl+Lb+lvOBqWR8 BiiSL8cv9U0XdqZuAvvJNIdTCDiz/aJd86XbmY3h6XWETKVetxjxoAMUw3eB7xcoX3+0 TkapeP0BhKcetlQekNq6tY5Qb6lXasbIgulScjvtiDkjKT8XEDOp8GY2SQhRzPFcN4tb CdYGfVup1XTEo+0b3YWZXpnxoDwdO9pDwNAKs2vwinSNyChTI4spEGrFptQ00ovMQa31 OERpDy8sOnJ9ffK6NpblUdGN5heTsQCtnM+NX/zFBCIk0VYQIo8YX9wGLK5s6/nav/Hu L44w== X-Forwarded-Encrypted: i=1; AHgh+RrOKtVxPbj9atvSQYMVvDndzVkBrYsUYe8uZ+HiwoBAu65vKeKcTLjEnyj02J0YHND0BSNOuDdoCTXAyLs=@vger.kernel.org X-Gm-Message-State: AOJu0YxqlNEHdsYWG9Z8l9HdlulutRWLa9uyHoyKyrh4pFmhxRupYPo6 NnBLAr/kNntukueCj0iEDEqtkj2jVf6Hd2U+ASjnscYVm5++IcxwLQjAfMyEmV8eobw= X-Gm-Gg: AfdE7ck9EgjJS9+ZqOBLYPQWbmU2HHJVBBDrDTSDFRC89HbqDky9ePfJLCI3l+yv9RS r5sBgfJZZAtMEL5eRh67DAy9NLTyP7rZSmMA+ptx6lkqqgz08G21lDyuNQbXuLR/NUb8WM4zNct qd/z3vH4OBjjF2Zt2OupfTUpGc172iQNlqT9Vya7Lodc9H1MMVCZlveCjs1RUSlqHKyJ27yq7qs WZGm1Q3+JD7UNcYYsJeO+Iy1EvjhkzIB1F1zO/XhJZO8piXnM8cJs6Og8+aVRRqeLaO89VzICCl q2sAyJd1n96s6Eo3+rFk3l8T8DiTeotFGWPNHSTbi4eP5sE65IK9EAmEN1YA9fHlnxFbR4fgPmU gduD59oMQf5+MsddvlmtJynya5kr2AycOI9Zd67Hd5PZQ71+qumuHcvCiEHb09W/cM+KdnYRTJY OnOK+yLKc5tYp/5O2exdVTsdZAeWV/VE/CVIP92HSVAWHTmNt0/wK9wZJhC/ieiJw0xg== X-Received: by 2002:a05:6000:2dc9:b0:475:f100:35fe with SMTP id ffacd0b85a97d-47f2dd475e0mr23261709f8f.59.1784196841385; Thu, 16 Jul 2026 03:14:01 -0700 (PDT) Received: from localhost (p200300f65f47db046a548a0537ec1e67.dip0.t-ipconnect.de. [2003:f6:5f47:db04:6a54:8a05:37ec:1e67]) by smtp.gmail.com with UTF8SMTPSA id ffacd0b85a97d-47f4634debesm23440465f8f.8.2026.07.16.03.14.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 16 Jul 2026 03:14:00 -0700 (PDT) Date: Thu, 16 Jul 2026 12:13:59 +0200 From: Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= To: Mark Brown Cc: "Martin K. Petersen" , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: manual merge of the scsi-mkp tree with the origin tree Message-ID: References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qf5pzw55mbyul4ky" Content-Disposition: inline In-Reply-To: --qf5pzw55mbyul4ky Content-Type: text/plain; protected-headers=v1; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: linux-next: manual merge of the scsi-mkp tree with the origin tree MIME-Version: 1.0 Hello Mark, On Mon, Jul 13, 2026 at 04:13:24PM +0100, Mark Brown wrote: > Today's linux-next merge of the scsi-mkp tree got a conflict in: >=20 > include/linux/mod_devicetable.h >=20 > between commit: >=20 > ad428f5811bd7 ("mod_devicetable.h: Split into per subsystem headers") >=20 > from the origin tree and commit: >=20 > e73ba3d6ed03b ("scsi: zorro: Simplify storing pointers in device id str= uct") >=20 > from the scsi-mkp tree. >=20 > 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. >=20 > diff --cc include/linux/mod_devicetable.h > index a397213bedace,2673a1bd82c45..0000000000000 > --- a/include/linux/mod_devicetable.h > +++ b/include/linux/mod_devicetable.h > diff --git a/include/linux/device-id/zorro.h b/include/linux/device-id/zo= rro.h > index 5fdac81689839..26827b9b90b67 100644 > --- a/include/linux/device-id/zorro.h > +++ b/include/linux/device-id/zorro.h > @@ -13,7 +13,11 @@ typedef unsigned long kernel_ulong_t; > =20 > struct zorro_device_id { > __u32 id; /* Device ID or ZORRO_WILDCARD */ > - kernel_ulong_t driver_data; /* Data private to the driver */ > + union { > + /* Data private to the driver */ > + kernel_ulong_t driver_data; > + const void *driver_data_ptr; > + }; > }; While this looks right, I think it's wrong in git: $ git show next-20260715~32 commit b36e50419ebc00bef45b574c6ce3e7edbbda5eb9 Merge: 20361c12febf cf1af0ccca54 Author: Mark Brown Date: Wed Jul 15 14:23:48 2026 +0100 Merge branch 'for-next' of https://git.kernel.org/pub/scm/linux/kernel/= git/jejb/scsi.git diff --cc include/linux/device-id/zorro.h index 5fdac8168983,000000000000..26827b9b90b6 mode 100644,000000..100644 --- a/include/linux/device-id/zorro.h +++ b/include/linux/device-id/zorro.h @@@ -1,19 -1,0 +1,23 @@@ +/* SPDX-License-Identifier: GPL-2.0 */ +#ifndef LINUX_DEVICE_ID_ZORRO_H +#define LINUX_DEVICE_ID_ZORRO_H + +#ifdef __KERNEL__ +#include +typedef unsigned long kernel_ulong_t; +#endif + +#define ZORRO_WILDCARD (0xffffffff) /* not offi= cial */ + +#define ZORRO_DEVICE_MODALIAS_FMT "zorro:i%08X" + +struct zorro_device_id { + __u32 id; /* Device ID or ZORRO_WILDCARD */ - kernel_ulong_t driver_data; /* Data private to the driver */ ++ union { ++ /* Data private to the driver */ ++ kernel_ulong_t driver_data; ++ const void *driver_data_ptr; ++ }; +}; + +#endif /* ifndef LINUX_DEVICE_ID_ZORRO_H */ So the fixup is applied to the merge of the scsi tree and not the scsi-mkp tree. The latter wasn't pulled into next-20260715 at all. Given that e73ba3d6ed03b isn't in next, the fixup shouldn't be there either. Looking at merge.log I see merging scsi-mkp is tried, the fixup is applied, yielding 0fd66dadace89 and then `git reset --hard HEAD^` follows throwing away that commit to replace it by next-20260714/scsi-mkp which is already included and thus the patches/device-id-zorro fixup is applied to the wrong commit. Having said that e73ba3d6ed03b is still in https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next without the patch preparing drivers/ata/pata_buddha.c for that change and thus resulting in a build failure on m68k. Best regards Uwe --qf5pzw55mbyul4ky Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEP4GsaTp6HlmJrf7Tj4D7WH0S/k4FAmpYruUACgkQj4D7WH0S /k7NgAgAk3ypt7pMjdm0gi5696Gfg8dQebe2C0am53pXzdO4tDaRzv3ypxm0bq5B omOfnQMhiLRYMRmBOKouzvLjSmCTepRhKIKuCUacijF4o5QKybq56cRsoGrIrsOr iRSyU19MCzJIqi7yXL+NSIhzBO0gVAeSbqKR82xDtBpzSw4iNt9tFErEh05OeQX/ 2sc8ZTZeqc3MxDS0Hyak2jjo9tHyiWU9QTCYeyouHuvVvblidi9DCBLRf13Jybrw FBLKV7LvL4FPBYA9/BUxXGWgVthtjop12tyjvv4MznKQ+KSL/ASx0iwG0MLm/Hu4 R5qxuIL8in/A2NhcH1yzcwDyZTwbNw== =kZDQ -----END PGP SIGNATURE----- --qf5pzw55mbyul4ky--