mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Wei Liu <wei.liu@kernel.org>, Christian Brauner <brauner@kernel.org>
Cc: Jinank Jain <jinankjain@microsoft.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Muminul Islam <muislam@microsoft.com>,
	Nuno Das Neves <nunodasneves@linux.microsoft.com>
Subject: linux-next: manual merge of the hyperv tree with the vfs-brauner tree
Date: Tue, 25 Nov 2025 17:11:30 +1100	[thread overview]
Message-ID: <20251125171130.67ba74e1@canb.auug.org.au> (raw)

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

Hi all,

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

  drivers/hv/mshv_root_main.c

between commit:

  12692f6b7689 ("hv: convert mshv_ioctl_create_partition() to FD_ADD()")

from the vfs-brauner tree and commit:

  c91fe5f162f2 ("mshv: Extend create partition ioctl to support cpu features")

from the hyperv 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 drivers/hv/mshv_root_main.c
index 1d8d8d00e4e0,bc15d6f6922f..000000000000
--- a/drivers/hv/mshv_root_main.c
+++ b/drivers/hv/mshv_root_main.c
@@@ -1900,6 -1974,26 +1977,24 @@@ static long mshv_ioctl_process_pt_flags
  		break;
  	}
  
+ 	return 0;
+ }
+ 
+ static long
+ mshv_ioctl_create_partition(void __user *user_arg, struct device *module_dev)
+ {
+ 	u64 creation_flags;
+ 	struct hv_partition_creation_properties creation_properties;
+ 	union hv_partition_isolation_properties isolation_properties;
+ 	struct mshv_partition *partition;
 -	struct file *file;
 -	int fd;
+ 	long ret;
+ 
+ 	ret = mshv_ioctl_process_pt_flags(user_arg, &creation_flags,
+ 					  &creation_properties,
+ 					  &isolation_properties);
+ 	if (ret)
+ 		return ret;
+ 
  	partition = kzalloc(sizeof(*partition), GFP_KERNEL);
  	if (!partition)
  		return -ENOMEM;

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

                 reply	other threads:[~2025-11-25  6:11 UTC|newest]

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:
  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=20251125171130.67ba74e1@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=brauner@kernel.org \
    --cc=jinankjain@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=muislam@microsoft.com \
    --cc=nunodasneves@linux.microsoft.com \
    --cc=wei.liu@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®