All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian Norris" <norris@broadcom.com>
To: linux-mtd@lists.infradead.org
Cc: Sneha Narnakaje <nsnehaprabha@ti.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Brian Norris <norris@broadcom.com>,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: [PATCH v2 0/2] Deprecate ECCGETLAYOUT
Date: Wed, 18 Aug 2010 11:06:44 -0700	[thread overview]
Message-ID: <1282154806-9420-1-git-send-email-norris@broadcom.com> (raw)
In-Reply-To: <4C5CA4A1.1040000@broadcom.com>

The following two patches are implementations of two different
strategies to deprecate the ioctl ECCGETLAYOUT. This ioctl is not
very useful and imposes restrictions on expanding the corresponding
kernel struct nand_ecclayout. Either patch will leave functionality
intact but allow the kernel-space layouts to expand in the future.

Strategy 1: Create new struct nand_ecclayout_l and convert all kernel
  code to use this struct.
Strategy 2: Rename old struct nand_ecclayout_user and modify
  nand_ecclayout to be used in the kernel only.

Either strategy employs a new function that will shrink the larger
layout to fit the size of the old one.

Please let me know if either of these will have unintended
consequences. I believe I have tested these sufficiently in both
simulation and hardware.

Thanks,
Brian

Brian Norris (2):
  mtd: nand: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT
  mtd: nand: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT

WARNING: multiple messages have this Message-ID (diff)
From: "Brian Norris" <norris@broadcom.com>
To: linux-mtd@lists.infradead.org
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>,
	"Artem Bityutskiy" <dedekind1@gmail.com>,
	"David Woodhouse" <dwmw2@infradead.org>,
	"Brian Norris" <norris@broadcom.com>,
	"Sneha Narnakaje" <nsnehaprabha@ti.com>
Subject: [PATCH v2 0/2] Deprecate ECCGETLAYOUT
Date: Wed, 18 Aug 2010 11:06:44 -0700	[thread overview]
Message-ID: <1282154806-9420-1-git-send-email-norris@broadcom.com> (raw)
In-Reply-To: <4C5CA4A1.1040000@broadcom.com>

The following two patches are implementations of two different
strategies to deprecate the ioctl ECCGETLAYOUT. This ioctl is not
very useful and imposes restrictions on expanding the corresponding
kernel struct nand_ecclayout. Either patch will leave functionality
intact but allow the kernel-space layouts to expand in the future.

Strategy 1: Create new struct nand_ecclayout_l and convert all kernel
  code to use this struct.
Strategy 2: Rename old struct nand_ecclayout_user and modify
  nand_ecclayout to be used in the kernel only.

Either strategy employs a new function that will shrink the larger
layout to fit the size of the old one.

Please let me know if either of these will have unintended
consequences. I believe I have tested these sufficiently in both
simulation and hardware.

Thanks,
Brian

Brian Norris (2):
  mtd: nand: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT
  mtd: nand: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT


  reply	other threads:[~2010-08-18 18:07 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05 17:53 NAND ECC Layout, sysfs question Brian Norris
2010-08-05 18:18 ` Artem Bityutskiy
2010-08-07  0:11   ` [PATCH] mtd: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT Brian Norris
2010-08-07  0:11     ` Brian Norris
2010-08-18 18:06     ` Brian Norris [this message]
2010-08-18 18:06       ` [PATCH v2 0/2] Deprecate ECCGETLAYOUT Brian Norris
2010-08-18 20:37       ` [PATCH v3 1/2] mtd: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT Brian Norris
2010-08-18 20:37         ` Brian Norris
2010-08-20  0:50       ` [PATCH v2 0/2] Deprecate ECCGETLAYOUT Shinya Kuribayashi
2010-08-20  0:50         ` Shinya Kuribayashi
2010-08-20 15:15         ` Brian Norris
2010-08-20 15:15           ` Brian Norris
2010-08-23  4:12           ` Shinya Kuribayashi
2010-08-23  4:12             ` Shinya Kuribayashi
2010-08-24 10:45           ` Artem Bityutskiy
2010-08-24 10:45             ` Artem Bityutskiy
2010-08-25  1:12             ` [PATCH v4] mtd: nand: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT Brian Norris
2010-08-25  1:12               ` Brian Norris
2010-08-30 10:20               ` Artem Bityutskiy
2010-08-30 10:20                 ` Artem Bityutskiy
2010-09-18 17:24                 ` Artem Bityutskiy
2010-09-18 17:24                   ` Artem Bityutskiy
2010-09-18 20:03                   ` Brian Norris
2010-09-18 20:03                     ` Brian Norris
2010-09-19  7:17                     ` Artem Bityutskiy
2010-09-19  7:17                       ` Artem Bityutskiy
2010-09-20  6:28                   ` Brian Norris
2010-09-20  6:28                     ` Brian Norris
2010-09-20  6:57                     ` [PATCH] mtd: Edit comments on deprecation of " Brian Norris
2010-09-20  6:57                       ` Brian Norris
2010-09-20  8:49                       ` Artem Bityutskiy
2010-09-20  8:49                         ` Artem Bityutskiy
2010-09-20  7:52                     ` [PATCH v4] mtd: nand: Expand nand_ecc_layout, deprecate " Artem Bityutskiy
2010-09-20  7:52                       ` Artem Bityutskiy
2010-08-24 10:42       ` [PATCH v2 0/2] Deprecate ECCGETLAYOUT Artem Bityutskiy
2010-08-24 10:42         ` Artem Bityutskiy
2010-08-18 18:06     ` [PATCH v2 1/2] mtd: nand: Expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT Brian Norris
2010-08-18 18:06       ` Brian Norris
2010-08-18 18:06     ` [PATCH v2 2/2] " Brian Norris
2010-08-18 18:06       ` Brian Norris

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=1282154806-9420-1-git-send-email-norris@broadcom.com \
    --to=norris@broadcom.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nsnehaprabha@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.