From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Hans de Goede" <hdegoede@redhat.com>,
"Mark Gross" <markgross@kernel.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: Re: linux-next: manual merge of the driver-core tree with the drivers-x86 tree
Date: Thu, 7 Nov 2024 09:51:28 +0100 [thread overview]
Message-ID: <2024110719-detective-directly-fbcf@gregkh> (raw)
In-Reply-To: <20241107194007.1d247bde@canb.auug.org.au>
On Thu, Nov 07, 2024 at 07:40:07PM +1100, Stephen Rothwell wrote:
> 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;
>
Change looks good, thanks!
greg k-h
next prev parent reply other threads:[~2024-11-07 8:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 8:40 linux-next: manual merge of the driver-core tree with the drivers-x86 tree Stephen Rothwell
2024-11-07 8:51 ` Greg KH [this message]
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=2024110719-detective-directly-fbcf@gregkh \
--to=greg@kroah.com \
--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=sfr@canb.auug.org.au \
--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