From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Kevin Cernekee <cernekee@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Sneha Narnakaje <nsnehaprabha@ti.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Shinya Kuribayashi <shinya.kuribayashi.px@renesas.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: Edit comments on deprecation of ioctl ECCGETLAYOUT
Date: Mon, 20 Sep 2010 11:49:12 +0300 [thread overview]
Message-ID: <1284972552.2286.51.camel@localhost> (raw)
In-Reply-To: <4C9705C8.4090603@gmail.com>
On Sun, 2010-09-19 at 23:57 -0700, Brian Norris wrote:
> ** Applies to l2-mtd-2.6.git: master **
>
> There were some improvements and additions necessary in the
> comments explaining of the expansion of nand_ecclayout, the
> introduction of nand_ecclayout_user, and the deprecation of the
> ioctl ECCGETLAYOUT.
>
> Also, I found a better placement for the macro MTD_MAX_ECCPOS_ENTRIES;
> next to the definition of MTD_MAX_OOBFREE_ENTRIES in mtd-abi.h. The macro
> is really only important for the ioctl code (found in drivers/mtd/mtdchar.c)
> but since there are small edits being made to the user-space header, I
> figured this is a better location.
>
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Pushed to l2-mtd-2.6.git / master, thanks.
Note, I rebased the l2 tree an put this patch next to the "parent"
patch:
commit 728d7eef6c0ff50cb9b327ff7c02830c707f2bbc
Author: Brian Norris <computersforpeace@gmail.com>
Date: Tue Aug 24 18:12:00 2010 -0700
mtd: nand: expand nand_ecc_layout, deprecate ioctl ECCGETLAYOUT
This is just more logical to keep them together.
Thanks!
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-09-20 8:51 UTC|newest]
Thread overview: 21+ 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-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-20 0:50 ` [PATCH v2 0/2] Deprecate ECCGETLAYOUT Shinya Kuribayashi
2010-08-20 15:15 ` Brian Norris
2010-08-23 4:12 ` Shinya Kuribayashi
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-30 10:20 ` Artem Bityutskiy
2010-09-18 17:24 ` Artem Bityutskiy
2010-09-18 20:03 ` Brian Norris
2010-09-19 7:17 ` Artem Bityutskiy
2010-09-20 6:28 ` Brian Norris
2010-09-20 6:57 ` [PATCH] mtd: Edit comments on deprecation of " Brian Norris
2010-09-20 8:49 ` Artem Bityutskiy [this message]
2010-09-20 7:52 ` [PATCH v4] mtd: nand: Expand nand_ecc_layout, deprecate " Artem Bityutskiy
2010-08-24 10:42 ` [PATCH v2 0/2] Deprecate ECCGETLAYOUT 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 ` [PATCH v2 2/2] " 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=1284972552.2286.51.camel@localhost \
--to=dedekind1@gmail.com \
--cc=cernekee@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nsnehaprabha@ti.com \
--cc=shinya.kuribayashi.px@renesas.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).