Linux-Next Archive on
 help / color / Atom feed
From: Stephen Rothwell <>
To: Miguel Ojeda <>,
	Petr Mladek <>
Cc: Adam Bratschi-Kaye <>,
	Alex Gaynor <>, Finn Behrens <>,
	Geoffrey Thomas <>,
	John Ogness <>,
	Linux Kernel Mailing List <>,
	Linux Next Mailing List <>,
	Michael Ellerman <>,
	Miguel Ojeda <>,
	Wedson Almeida Filho <>
Subject: linux-next: manual merge of the rust tree with the printk tree
Date: Fri, 16 Apr 2021 18:07:00 +1000
Message-ID: <> (raw)

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

Hi all,

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


between commit:

  cf5b0208fda4 ("printk: introduce CONSOLE_LOG_MAX")

from the printk tree and commit:

  fd1e637b9b4b ("Rust: Kernel crate")

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

Stephen Rothwell

diff --cc kernel/printk/printk.c
index 421c35571797,d13be89530c4..000000000000
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@@ -394,11 -411,8 +394,12 @@@ static struct latched_seq clear_seq = 
  #define PREFIX_MAX		32
 +/* the maximum size of a formatted record (i.e. with prefix added per line) */
 +#define CONSOLE_LOG_MAX		1024
 +/* the maximum size allowed to be reserved for a record */
+ /* Keep in sync with rust/kernel/ */
 -#define LOG_LINE_MAX		(1024 - PREFIX_MAX)
  #define LOG_LEVEL(v)		((v) & 0x07)
  #define LOG_FACILITY(v)		((v) >> 3 & 0xff)

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

                 reply index

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Next Archive on

Archives are clonable:
	git clone --mirror linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ \
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone