From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Greg KH <greg@kroah.com>
Cc: dwmw2@infradead.org, dedekind1@gmail.com,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 16/16] mtd/docg3: add protection areas sysfs access
Date: Sun, 27 Nov 2011 11:29:28 +0100 [thread overview]
Message-ID: <87r50t3lkn.fsf@free.fr> (raw)
In-Reply-To: <20111126235727.GA12856@kroah.com> (Greg KH's message of "Sat, 26 Nov 2011 15:57:27 -0800")
Greg KH <greg@kroah.com> writes:
> On Sat, Nov 19, 2011 at 04:02:58PM +0100, Robert Jarzmik wrote:
>> As each docg3 chip has 2 protection areas (DPS0 and DPS1),
>> and because theses areas can prevent user access to the chip
>> data, add for each floor the sysfs entries which insert the
>> protection key into the right DPS.
>>
>> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
>
> As you are adding new sysfs files, you also must add Documentation/ABI
> entries for them. Please do so.
OK Greg, I'll prepare a patch soon.
Cheers.
--
Robert
next prev parent reply other threads:[~2011-11-27 10:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 15:02 [PATCH v3 00/16] DocG3 fixes and write support Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 01/16] mtd/docg3: fix debug log verbosity Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 02/16] mtd/docg3: fix tracing of IO in writeb Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 03/16] mtd/docg3: fix protection areas reading Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 04/16] mtd/docg3: fix BCH registers Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 05/16] mtd/docg3: fix reading oob+data without correction Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 06/16] mtd/docg3: add multiple floor support Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 07/16] mtd/docg3: add OOB layout to mtdinfo Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 08/16] mtd/docg3: add registers for erasing and writing Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 09/16] mtd/docg3: add OOB buffer to device structure Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 10/16] mtd/docg3: add write functions Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 11/16] mtd/docg3: add erase functions Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 12/16] mtd/docg3: map erase and write functions Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 13/16] mtd/docg3: add ECC correction code Robert Jarzmik
2011-11-24 10:24 ` Ivan Djelic
2011-11-24 17:56 ` Mike Dunn
2011-11-19 15:02 ` [PATCH v3 14/16] mtd/docg3: add suspend and resume Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 15/16] mtd/docg3: add fast mode Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 16/16] mtd/docg3: add protection areas sysfs access Robert Jarzmik
2011-11-26 23:57 ` Greg KH
2011-11-27 10:29 ` Robert Jarzmik [this message]
2011-11-22 21:29 ` [PATCH v3 00/16] DocG3 fixes and write support Artem Bityutskiy
2011-11-25 17:44 ` Robert Jarzmik
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=87r50t3lkn.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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