public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Zhen Ni <nizhen@uniontech.com>
Subject: Re: linux-next: manual merge of the sysctl tree with the rcu tree
Date: Wed, 20 Apr 2022 09:24:25 -0700	[thread overview]
Message-ID: <20220420162425.GF4285@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20220420153746.4790d532@canb.auug.org.au>

On Wed, Apr 20, 2022 at 03:37:46PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the sysctl tree got a conflict in:
> 
>   kernel/rcu/rcu.h
> 
> between commit:
> 
>   95d4e9e339d1 ("rcu: Provide a get_completed_synchronize_rcu() function")
> 
> from the rcu tree and commit:
> 
>   d9ab0e63fa7f ("sched: Move rt_period/runtime sysctls to rt.c")
> 
> from the sysctl 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.

Thank you, Stephen!  I have this one marked down.

							Thanx, Paul

> -- 
> Cheers,
> Stephen Rothwell
> 
> diff --cc kernel/rcu/rcu.h
> index 15b96f990774,7812c740b3bf..000000000000
> --- a/kernel/rcu/rcu.h
> +++ b/kernel/rcu/rcu.h
> @@@ -23,9 -23,8 +23,11 @@@
>   #define RCU_SEQ_CTR_SHIFT	2
>   #define RCU_SEQ_STATE_MASK	((1 << RCU_SEQ_CTR_SHIFT) - 1)
>   
>  +/* Low-order bit definition for polled grace-period APIs. */
>  +#define RCU_GET_STATE_COMPLETED	0x1
>  +
> + extern int sysctl_sched_rt_runtime;
> + 
>   /*
>    * Return the counter portion of a sequence number previously returned
>    * by rcu_seq_snap() or rcu_seq_current().



      reply	other threads:[~2022-04-20 16:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  5:37 linux-next: manual merge of the sysctl tree with the rcu tree Stephen Rothwell
2022-04-20 16:24 ` Paul E. McKenney [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=20220420162425.GF4285@paulmck-ThinkPad-P17-Gen-1 \
    --to=paulmck@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=nizhen@uniontech.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