linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Shelton <ben.shelton@ni.com>
To: dwmw2@infradead.org, computersforpeace@gmail.com,
	dedekind1@gmail.com, adrian.hunter@intel.com,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: joshc@ni.com, xander.huff@ni.com, punnaiah.choudary.kalluri@xilinx.com
Subject: Adding subpage support to NAND driver -- backwards compatibility concerns
Date: Wed, 22 Apr 2015 12:29:44 -0500	[thread overview]
Message-ID: <20150422172944.GA4134@bshelton-desktop> (raw)

Hi all,

We're currently carrying a patch out of tree to add subpage read and
write support to the pl353_nand driver.  Xilinx is currently working to
mainline this driver; see

http://www.spinics.net/lists/devicetree/msg76307.html

We'd like to upstream our patch, but my concern is that UBIFS behaves
differently when it knows that the flash device supports subpages.  I
have a couple of questions related to that:

- I know from experience that bad things happen when you use a kernel
  without subpage support with an UBIFS filesystem that was formatted
  with subpage support.  Is it safe to do the opposite (kernel with
  subpage support / UBIFS filesystem formatted without subpage support)?

- Assuming that it isn't safe, what's the best way to add subpage
  support to this driver in an upstreamable way / without breaking
  people?  Would it be sufficient to add subpage support as a Kconfig
  option that's disabled by default with a strongly-worded message
  describing the consequences of enabling it?

Thanks,
Ben

             reply	other threads:[~2015-04-22 17:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 17:29 Ben Shelton [this message]
2015-04-23  2:48 ` Adding subpage support to NAND driver -- backwards compatibility concerns Iwo Mergler
2015-04-23 18:39   ` Josh Cartwright
2015-04-23 19:30     ` Richard Weinberger
2015-04-23 23:13       ` Iwo Mergler
2015-04-23 23:32         ` Richard Weinberger

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=20150422172944.GA4134@bshelton-desktop \
    --to=ben.shelton@ni.com \
    --cc=adrian.hunter@intel.com \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=joshc@ni.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=punnaiah.choudary.kalluri@xilinx.com \
    --cc=xander.huff@ni.com \
    /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).