LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	"\"Jörn Engel\"" <joern@logfs.org>,
	"Ben Hutchings" <bhutchings@solarflare.com>,
	"Artem Bityutskiy" <Artem.Bityutskiy@nokia.com>
Subject: linux-next: manual merge of the mtd tree with Linus' tree
Date: Thu, 29 Apr 2010 12:58:39 +1000	[thread overview]
Message-ID: <20100429125839.9dedf349.sfr@canb.auug.org.au> (raw)

Hi David,

Today's linux-next merge of the mtd tree got a conflict in
drivers/mtd/mtdcore.c between commit
a33eb6b91034c95b9b08576f68be170f995b2c7d ("Move mtd_bdi_*mappable to
mtdcore.c") from Linus' tree and commit
b520e412faaaad35641aeedd6059179f9f1b393c ("mtd: Replace static array of
devices with an idr structure") from the mtd tree.

Just overlapping additions.  I fixed it up (see below) and can carry the
fix for a while.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc drivers/mtd/mtdcore.c
index b177e75,70a7858..0000000
--- a/drivers/mtd/mtdcore.c
+++ b/drivers/mtd/mtdcore.c
@@@ -19,39 -17,12 +19,40 @@@
  #include <linux/init.h>
  #include <linux/mtd/compatmac.h>
  #include <linux/proc_fs.h>
 +#include <linux/backing-dev.h>
+ #include <linux/idr.h>
  
  #include <linux/mtd/mtd.h>
 -#include "internal.h"
  
  #include "mtdcore.h"
 +/*
 + * backing device capabilities for non-mappable devices (such as NAND flash)
 + * - permits private mappings, copies are taken of the data
 + */
 +struct backing_dev_info mtd_bdi_unmappable = {
 +	.capabilities	= BDI_CAP_MAP_COPY,
 +};
 +
 +/*
 + * backing device capabilities for R/O mappable devices (such as ROM)
 + * - permits private mappings, copies are taken of the data
 + * - permits non-writable shared mappings
 + */
 +struct backing_dev_info mtd_bdi_ro_mappable = {
 +	.capabilities	= (BDI_CAP_MAP_COPY | BDI_CAP_MAP_DIRECT |
 +			   BDI_CAP_EXEC_MAP | BDI_CAP_READ_MAP),
 +};
 +
 +/*
 + * backing device capabilities for writable mappable devices (such as RAM)
 + * - permits private mappings, copies are taken of the data
 + * - permits non-writable shared mappings
 + */
 +struct backing_dev_info mtd_bdi_rw_mappable = {
 +	.capabilities	= (BDI_CAP_MAP_COPY | BDI_CAP_MAP_DIRECT |
 +			   BDI_CAP_EXEC_MAP | BDI_CAP_READ_MAP |
 +			   BDI_CAP_WRITE_MAP),
 +};
  
  static int mtd_cls_suspend(struct device *dev, pm_message_t state);
  static int mtd_cls_resume(struct device *dev);

             reply	other threads:[~2010-04-29  2:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29  2:58 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-17  4:49 Stephen Rothwell
2021-08-17  8:15 ` Sean Young
2021-08-17  8:41   ` Miquel Raynal
2019-01-29  0:17 Stephen Rothwell
2019-01-29 14:12 ` Boris Brezillon
2011-05-27  4:00 Stephen Rothwell
2011-05-27  7:47 ` Artem Bityutskiy
2011-05-27  4:00 Stephen Rothwell
2011-05-27  7:43 ` Artem Bityutskiy
2010-10-26  0:32 Stephen Rothwell
2010-08-07  3:37 Stephen Rothwell
2009-06-01  4:00 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=20100429125839.9dedf349.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=bhutchings@solarflare.com \
    --cc=dwmw2@infradead.org \
    --cc=joern@logfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --subject='Re: linux-next: manual merge of the mtd tree with Linus'\'' 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).