mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: manual merge of the init tree with the block tree
Date: Fri, 17 Jul 2020 19:42:21 +1000	[thread overview]
Message-ID: <20200717194221.146ab662@canb.auug.org.au> (raw)

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

Hi all,

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

  drivers/md/md.c

between commit:

  a564e23f0f99 ("md: switch to ->check_events for media change notifications")

from the block tree and commit:

  7e0adbfc20c5 ("md: rewrite md_setup_drive to avoid ioctls")

from the init 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/md/md.c
index 5b6d46741baa,ee622b67424e..000000000000
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@@ -7836,21 -7790,23 +7820,21 @@@ static void md_release(struct gendisk *
  	mddev_put(mddev);
  }
  
 -static int md_media_changed(struct gendisk *disk)
 -{
 -	struct mddev *mddev = disk->private_data;
 -
 -	return mddev->changed;
 -}
 -
 -static int md_revalidate(struct gendisk *disk)
 +static unsigned int md_check_events(struct gendisk *disk, unsigned int clearing)
  {
  	struct mddev *mddev = disk->private_data;
 +	unsigned int ret = 0;
  
 +	if (mddev->changed)
 +		ret = DISK_EVENT_MEDIA_CHANGE;
  	mddev->changed = 0;
 -	return 0;
 +	return ret;
  }
 +
- static const struct block_device_operations md_fops =
+ const struct block_device_operations md_fops =
  {
  	.owner		= THIS_MODULE,
 +	.submit_bio	= md_submit_bio,
  	.open		= md_open,
  	.release	= md_release,
  	.ioctl		= md_ioctl,

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

             reply	other threads:[~2020-07-17  9:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17  9:42 Stephen Rothwell [this message]
2020-08-03  9:53 ` Stephen Rothwell
2020-08-04  2:44   ` 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=20200717194221.146ab662@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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®