linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>, Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>
Subject: linux-next: manual merge of the notifications tree with the vfs tree
Date: Mon, 25 May 2020 19:26:25 +1000	[thread overview]
Message-ID: <20200525192625.18ae7c9b@canb.auug.org.au> (raw)

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

Hi all,

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

  include/linux/pipe_fs_i.h

between commit:

  f6dd975583bd ("pipe: merge anon_pipe_buf*_ops")

from the vfs tree and commits:

  8cfba76383e9 ("pipe: Allow buffers to be marked read-whole-or-error for notifications")
  e7d553d69cf6 ("pipe: Add notification lossage handling")

from the notifications 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/pipe_fs_i.h
index 0c31b9461262,6626f511de6f..000000000000
--- a/include/linux/pipe_fs_i.h
+++ b/include/linux/pipe_fs_i.h
@@@ -8,7 -8,10 +8,11 @@@
  #define PIPE_BUF_FLAG_ATOMIC	0x02	/* was atomically mapped */
  #define PIPE_BUF_FLAG_GIFT	0x04	/* page is a gift */
  #define PIPE_BUF_FLAG_PACKET	0x08	/* read() as a packet */
 -#define PIPE_BUF_FLAG_WHOLE	0x10	/* read() must return entire buffer or error */
 +#define PIPE_BUF_FLAG_CAN_MERGE	0x10	/* can merge buffers */
++#define PIPE_BUF_FLAG_WHOLE	0x20	/* read() must return entire buffer or error */
+ #ifdef CONFIG_WATCH_QUEUE
 -#define PIPE_BUF_FLAG_LOSS	0x20	/* Message loss happened after this buffer */
++#define PIPE_BUF_FLAG_LOSS	0x40	/* Message loss happened after this buffer */
+ #endif
  
  /**
   *	struct pipe_buffer - a linux kernel pipe buffer

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

             reply	other threads:[~2020-05-25  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  9:26 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-15  9:40 Stephen Rothwell
2020-05-15  9:25 Stephen Rothwell

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=20200525192625.18ae7c9b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dhowells@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    --subject='Re: linux-next: manual merge of the notifications tree with the vfs tree' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).