mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Andreas Hindborg <a.hindborg@kernel.org>
Cc: FUJITA Tomonori <fujita.tomonori@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Miguel Ojeda <ojeda@kernel.org>
Subject: linux-next: manual merge of the rust-timekeeping tree with the rust tree
Date: Fri, 2 Oct 2026 12:58:18 +0100	[thread overview]
Message-ID: <ar-cWpOhcuo85ttt@sirena.org.uk> (raw)

Hi all,


  rust/kernel/Kconfig.test

between commit:

  cd56a1c858ff3 ("rust: bug: add a KUnit test for warn_on!")

from the rust tree and commit:

  a9aba476d42df ("rust: time: add Delta::to_jiffies_timeout() for timeout conversion")

from the rust-timekeeping 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 rust/kernel/Kconfig.test
index 966b07872ba15,0087749995d2b..0000000000000
--- a/rust/kernel/Kconfig.test
+++ b/rust/kernel/Kconfig.test
@@@ -83,12 -83,11 +83,18 @@@ config RUST_BITFIELD_KUNIT_TES
  
  	  If unsure, say N.
  
 +config RUST_BUG_KUNIT_TEST
 +	bool "KUnit tests for the Rust BUG/WARN functionality" if !KUNIT_ALL_TESTS
 +	depends on BUG
 +	default KUNIT_ALL_TESTS
 +	help
 +	  This option enables KUnit tests for the Rust BUG/WARN functionality.
++
+ config RUST_TIME_KUNIT_TEST
+ 	bool "KUnit tests for the Rust time API" if !KUNIT_ALL_TESTS
+ 	default KUNIT_ALL_TESTS
+ 	help
+ 	  This option enables KUnit tests for the Rust time API.
  	  These are only for development and testing, not for regular
  	  kernel use cases.
  

             reply	other threads:[~2026-10-02 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 11:58 Mark Brown [this message]
2026-10-02 12:24 ` Miguel Ojeda

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=ar-cWpOhcuo85ttt@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=fujita.tomonori@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ojeda@kernel.org \
    /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

all inboxes | Powered by JetHome®