linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>,
	Dan Williams <dan.j.williams@intel.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: manual merge of the akpm-current tree with the nvdimm tree
Date: Fri, 8 Jan 2016 16:51:21 +1100	[thread overview]
Message-ID: <20160108165121.312b7f77@canb.auug.org.au> (raw)

Hi Andrew,

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

  drivers/nvdimm/pmem.c

between commit:

  d0d852f68113 ("block: clarify badblocks lifetime")

from the nvdimm tree and commit:

  90283d3934a7 ("mm: introduce find_dev_pagemap()")

from the akpm-current tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc drivers/nvdimm/pmem.c
index 5e6656fa3f58,37ebf42c0415..000000000000
--- a/drivers/nvdimm/pmem.c
+++ b/drivers/nvdimm/pmem.c
@@@ -21,10 -21,10 +21,11 @@@
  #include <linux/init.h>
  #include <linux/platform_device.h>
  #include <linux/module.h>
- #include <linux/memory_hotplug.h>
  #include <linux/moduleparam.h>
 +#include <linux/badblocks.h>
+ #include <linux/memremap.h>
  #include <linux/vmalloc.h>
+ #include <linux/pfn_t.h>
  #include <linux/slab.h>
  #include <linux/pmem.h>
  #include <linux/nd.h>
@@@ -192,13 -180,8 +205,9 @@@ static int pmem_attach_disk(struct devi
  		struct nd_namespace_common *ndns, struct pmem_device *pmem)
  {
  	int nid = dev_to_node(dev);
 +	struct badblocks *bb;
  	struct gendisk *disk;
  
- 	pmem->pmem_queue = blk_alloc_queue_node(GFP_KERNEL, nid);
- 	if (!pmem->pmem_queue)
- 		return -ENOMEM;
- 
  	blk_queue_make_request(pmem->pmem_queue, pmem_make_request);
  	blk_queue_physical_block_size(pmem->pmem_queue, PAGE_SIZE);
  	blk_queue_max_hw_sectors(pmem->pmem_queue, UINT_MAX);

             reply	other threads:[~2016-01-08  5:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08  5:51 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-07  6:39 linux-next: manual merge of the akpm-current tree with the nvdimm tree Stephen Rothwell
2021-12-07  6:55 ` Christoph Hellwig
2021-12-07 10:23   ` Joao Martins
2018-06-04 10:24 Stephen Rothwell
2017-11-16  3:16 Stephen Rothwell
2017-11-16  4:55 ` Minchan Kim
2017-04-24  6:47 Stephen Rothwell
2015-12-31 10:51 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=20160108165121.312b7f77@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).