public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kees Cook <kees@kernel.org>, Andrew Morton <akpm@linux-foundation.org>
Cc: Hongbo Li <lihongbo22@huawei.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: linux-next: manual merge of the kspp tree with the mm tree
Date: Thu, 29 Aug 2024 15:31:45 +1000	[thread overview]
Message-ID: <20240829153145.7f768337@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]

Hi all,

Today's linux-next merge of the kspp tree got a conflict in:

  include/linux/string_choices.h

between commit:

  533f2ca2a8a2 ("lib/string_choices: add str_true_false()/str_false_true() helper")

from the mm-nonmm-unstable branch of the mm tree and commits:

  a98ae7f045b2 ("lib/string_choices: Add str_up_down() helper")
  f5c1ca3a15fd ("string_choices: Add wrapper for str_down_up()")

from the kspp 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 include/linux/string_choices.h
index 4a2432313b8e,1320bcdcb89c..000000000000
--- a/include/linux/string_choices.h
+++ b/include/linux/string_choices.h
@@@ -42,12 -42,12 +42,18 @@@ static inline const char *str_yes_no(bo
  	return v ? "yes" : "no";
  }
  
 +static inline const char *str_true_false(bool v)
 +{
 +	return v ? "true" : "false";
 +}
 +#define str_false_true(v)		str_true_false(!(v))
 +
+ static inline const char *str_up_down(bool v)
+ {
+ 	return v ? "up" : "down";
+ }
+ #define str_down_up(v)		str_up_down(!(v))
+ 
  /**
   * str_plural - Return the simple pluralization based on English counts
   * @num: Number used for deciding pluralization

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-08-29  5:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29  5:31 Stephen Rothwell [this message]
2024-08-29  8:12 ` linux-next: manual merge of the kspp tree with the mm tree Hongbo Li
  -- strict thread matches above, loose matches on Subject: below --
2024-02-22  5:41 Stephen Rothwell
2024-02-22 17:11 ` Andrew Morton

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=20240829153145.7f768337@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=kees@kernel.org \
    --cc=lihongbo22@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=michal.wajdeczko@intel.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