From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>
Subject: Re: linux-next: manual merge of the driver-core tree with the s390 tree
Date: Tue, 21 Mar 2023 08:39:59 +0100 [thread overview]
Message-ID: <ZBlfT3mb5Kmuyh4I@kroah.com> (raw)
In-Reply-To: <20230321123428.5c6956f8@canb.auug.org.au>
On Tue, Mar 21, 2023 at 12:34:28PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the driver-core tree got a conflict in:
>
> arch/s390/kernel/topology.c
>
> between commit:
>
> 0599331c3da6 ("s390: simplify one-level sysctl registration for topology_ctl_table")
>
> from the s390 tree and commit:
>
> 9493ed19fbc3 ("s390/topology: move to use bus_get_dev_root()")
>
> 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 arch/s390/kernel/topology.c
> index e5d6a1c25d13,72af753d1bba..000000000000
> --- a/arch/s390/kernel/topology.c
> +++ b/arch/s390/kernel/topology.c
> @@@ -637,14 -637,33 +637,23 @@@ static struct ctl_table topology_ctl_ta
> { },
> };
>
> -static struct ctl_table topology_dir_table[] = {
> - {
> - .procname = "s390",
> - .maxlen = 0,
> - .mode = 0555,
> - .child = topology_ctl_table,
> - },
> - { },
> -};
> -
> static int __init topology_init(void)
> {
> + struct device *dev_root;
> + int rc = 0;
> +
> timer_setup(&topology_timer, topology_timer_fn, TIMER_DEFERRABLE);
> if (MACHINE_HAS_TOPOLOGY)
> set_topology_timer();
> else
> topology_update_polarization_simple();
> - register_sysctl_table(topology_dir_table);
> + register_sysctl("s390", topology_ctl_table);
> - return device_create_file(cpu_subsys.dev_root, &dev_attr_dispatching);
> +
> + dev_root = bus_get_dev_root(&cpu_subsys);
> + if (dev_root) {
> + rc = device_create_file(dev_root, &dev_attr_dispatching);
> + put_device(dev_root);
> + }
> + return rc;
> }
> device_initcall(topology_init);
Looks correct to me, thanks!
greg k-h
next prev parent reply other threads:[~2023-03-21 7:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 1:34 linux-next: manual merge of the driver-core tree with the s390 tree Stephen Rothwell
2023-03-21 7:39 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-28 6:26 Stephen Rothwell
2012-01-04 23:07 ` Greg KH
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=ZBlfT3mb5Kmuyh4I@kroah.com \
--to=greg@kroah.com \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.