From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Luis Chamberlain" <mcgrof@kernel.org>,
"Petr Pavlu" <petr.pavlu@suse.com>,
"Sami Tolvanen" <samitolvanen@google.com>,
"Daniel Gomez" <da.gomez@samsung.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>
Subject: Re: linux-next: manual merge of the driver-core tree with the modules tree
Date: Fri, 10 Jan 2025 15:04:43 +0100 [thread overview]
Message-ID: <2025011030-attempt-overkill-c0ae@gregkh> (raw)
In-Reply-To: <20250110144051.36796c49@canb.auug.org.au>
On Fri, Jan 10, 2025 at 02:40:51PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the driver-core tree got a conflict in:
>
> kernel/module/sysfs.c
>
> between commit:
>
> 9953f4227850 ("module: sysfs: Add notes attributes through attribute_group")
>
> from the modules tree and commit:
>
> 3675a926feef ("sysfs: constify bin_attribute argument of sysfs_bin_attr_simple_read()")
>
> from the driver-core 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 kernel/module/sysfs.c
> index f99616499e2e,254017b58b64..000000000000
> --- a/kernel/module/sysfs.c
> +++ b/kernel/module/sysfs.c
> @@@ -190,8 -196,8 +190,8 @@@ static int add_notes_attrs(struct modul
> nattr->attr.mode = 0444;
> nattr->size = info->sechdrs[i].sh_size;
> nattr->private = (void *)info->sechdrs[i].sh_addr;
> - nattr->read = sysfs_bin_attr_simple_read;
> + nattr->read_new = sysfs_bin_attr_simple_read;
> - ++nattr;
> + *(gattr++) = nattr++;
> }
> ++loaded;
> }
Looks good to me, thanks.
greg k-h
prev parent reply other threads:[~2025-01-10 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 3:40 linux-next: manual merge of the driver-core tree with the modules tree Stephen Rothwell
2025-01-10 14:04 ` Greg KH [this message]
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=2025011030-attempt-overkill-c0ae@gregkh \
--to=greg@kroah.com \
--cc=da.gomez@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=sfr@canb.auug.org.au \
/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