From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>, Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Suma Hegde" <suma.hegde@amd.com>,
"Thomas Weißschuh" <linux@weissschuh.net>
Subject: linux-next: manual merge of the driver-core tree with the drivers-x86 tree
Date: Thu, 7 Nov 2024 19:40:07 +1100 [thread overview]
Message-ID: <20241107194007.1d247bde@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]
Hi all,
Today's linux-next merge of the driver-core tree got a conflict in:
drivers/platform/x86/amd/hsmp.c
between commit:
9df193087b9e ("platform/x86/amd/hsmp: Create hsmp/ directory")
from the drivers-x86 tree and commit:
b626816fdd7f ("sysfs: treewide: constify attribute callback of bin_is_visible()")
from the driver-core tree.
I fixed it up (I deleted the file and applied the following patch) 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.
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu, 7 Nov 2024 19:36:12 +1100
Subject: [PATCH] fix up for "sysfs: treewide: constify attribute callback of
bin_is_visible()"
interacting with "platform/x86/amd/hsmp: Create hsmp/ directory" from
the drivers-x86 tree.
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
drivers/platform/x86/amd/hsmp/plat.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/platform/x86/amd/hsmp/plat.c b/drivers/platform/x86/amd/hsmp/plat.c
index f8e74c0392ba..748bbc356484 100644
--- a/drivers/platform/x86/amd/hsmp/plat.c
+++ b/drivers/platform/x86/amd/hsmp/plat.c
@@ -75,7 +75,7 @@ static ssize_t hsmp_metric_tbl_plat_read(struct file *filp, struct kobject *kobj
}
static umode_t hsmp_is_sock_attr_visible(struct kobject *kobj,
- struct bin_attribute *battr, int id)
+ const struct bin_attribute *battr, int id)
{
u16 sock_ind;
--
2.45.2
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-11-07 8:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 8:40 Stephen Rothwell [this message]
2024-11-07 8:51 ` linux-next: manual merge of the driver-core tree with the drivers-x86 tree Greg KH
2024-11-07 10:26 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2020-03-23 3:38 Stephen Rothwell
2020-03-23 9:57 ` Greg KH
2020-03-23 11:43 ` Andy Shevchenko
2020-04-01 3:11 ` Stephen Rothwell
2020-04-01 6:47 ` Andy Shevchenko
2020-04-01 7:18 ` Stephen Rothwell
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=20241107194007.1d247bde@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=markgross@kernel.org \
--cc=suma.hegde@amd.com \
/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