diff mbox series

linux-next: manual merge of the ext4 tree with Linus' tree

Message ID 20230627103900.04fa564f@canb.auug.org.au
State New
Headers
Series linux-next: manual merge of the ext4 tree with Linus' tree |

Commit Message

Stephen Rothwell June 27, 2023, 12:39 a.m. UTC 
  Hi all,

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

  fs/ext4/ioctl.c

between commit:

  97524b454bc5 ("ext4: split ext4_shutdown")

from Linus' tree and commit:

  c4d13222afd8 ("ext4: fix to check return value of freeze_bdev() in ext4_shutdown()")

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

Comments

Christoph Hellwig June 27, 2023, 6:37 a.m. UTC | #1 
On Tue, Jun 27, 2023 at 10:39:00AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the ext4 tree got a conflict in:
> 
>   fs/ext4/ioctl.c
> 
> between commit:
> 
>   97524b454bc5 ("ext4: split ext4_shutdown")
> 
> from Linus' tree and commit:
> 
>   c4d13222afd8 ("ext4: fix to check return value of freeze_bdev() in ext4_shutdown()")

Hmm, I can't actually find the latter commit in linux-next and the context
below also doesn't make it obviously cler to me what the conflict was.
Stephen Rothwell June 27, 2023, 7:26 a.m. UTC | #2 
Hi Christoph,

On Tue, 27 Jun 2023 08:37:53 +0200 Christoph Hellwig <hch@lst.de> wrote:
>
> On Tue, Jun 27, 2023 at 10:39:00AM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Today's linux-next merge of the ext4 tree got a conflict in:
> > 
> >   fs/ext4/ioctl.c
> > 
> > between commit:
> > 
> >   97524b454bc5 ("ext4: split ext4_shutdown")
> > 
> > from Linus' tree and commit:
> > 
> >   c4d13222afd8 ("ext4: fix to check return value of freeze_bdev() in ext4_shutdown()")  
> 
> Hmm, I can't actually find the latter commit in linux-next and the context
> below also doesn't make it obviously cler to me what the conflict was.

That is probably because today's tree had not been released yet ..
please refetch and try again.
diff mbox series

Patch

diff --cc fs/ext4/ioctl.c
index 961284cc9b65,55be1b8a6360..000000000000
--- a/fs/ext4/ioctl.c