public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Shuah Khan <shuah@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>,
	Clint George <clintbgeorge@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Ming Lei <ming.lei@redhat.com>,
	Uday Shankar <ushankar@purestorage.com>
Subject: linux-next: manual merge of the kselftest tree with the block tree
Date: Mon, 26 Jan 2026 22:14:48 +0000	[thread overview]
Message-ID: <aXfnWL8Wh5jKAE71@sirena.org.uk> (raw)

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

Hi all,

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

  tools/testing/selftests/ublk/kublk.h

between commit:

  584709ad5ce35 ("selftests: ublk: replace assert() with ublk_assert()")

from the block tree and commit:

  3e6ad272bb8b3 ("kselftest/kublk: include message in _Static_assert for C11 compatibility")

from the kselftest 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.

diff --cc tools/testing/selftests/ublk/kublk.h
index ca97deb5e2082,e5eb5f762c1c1..0000000000000
--- a/tools/testing/selftests/ublk/kublk.h
+++ b/tools/testing/selftests/ublk/kublk.h
@@@ -333,10 -217,10 +333,10 @@@ static inline __u64 build_user_data(uns
  		unsigned tgt_data, unsigned q_id, unsigned is_target_io)
  {
  	/* we only have 7 bits to encode q_id */
- 	_Static_assert(UBLK_MAX_QUEUES_SHIFT <= 7);
+ 	_Static_assert(UBLK_MAX_QUEUES_SHIFT <= 7, "UBLK_MAX_QUEUES_SHIFT must be <= 7");
 -	assert(!(tag >> 16) && !(op >> 8) && !(tgt_data >> 16) && !(q_id >> 7));
 +	ublk_assert(!(tag >> 16) && !(op >> 8) && !(tgt_data >> 16) && !(q_id >> 7));
  
 -	return tag | (op << 16) | (tgt_data << 24) |
 +	return tag | ((__u64)op << 16) | ((__u64)tgt_data << 24) |
  		(__u64)q_id << 56 | (__u64)is_target_io << 63;
  }
  

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

                 reply	other threads:[~2026-01-26 22:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=aXfnWL8Wh5jKAE71@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=clintbgeorge@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=shuah@kernel.org \
    --cc=ushankar@purestorage.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