Linux-Next Archive on
 help / color / Atom feed
* linux-next: manual merge of the set_fs tree with the tip tree
@ 2020-07-27 11:04 Stephen Rothwell
  0 siblings, 0 replies; only message in thread
From: Stephen Rothwell @ 2020-07-27 11:04 UTC (permalink / raw)
  To: Christoph Hellwig, Thomas Gleixner, Ingo Molnar, H. Peter Anvin,
	Peter Zijlstra
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Qinglang Miao

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

Hi all,

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


between commit:

  0f85c4805184 ("debugobjects: Convert to DEFINE_SHOW_ATTRIBUTE")

from the tip tree and commit:

  4d4901c6d748 ("seq_file: switch over direct seq_read method calls to seq_read_iter")

from the set_fs tree.

I fixed it up (I just used the former) 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

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-27 11:04 linux-next: manual merge of the set_fs tree with the tip tree Stephen Rothwell

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