From: David Woodhouse <dwmw2@infradead.org>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [-mm patch 3/4] AVR32 MTD: Mapping driver for the ATSTK1000board
Date: Fri, 15 Sep 2006 09:00:30 +0100 [thread overview]
Message-ID: <1158307230.24527.36.camel@pmac.infradead.org> (raw)
In-Reply-To: <20060915095629.22cf01f4@cad-250-152.norway.atmel.com>
On Fri, 2006-09-15 at 09:56 +0200, Haavard Skinnemoen wrote:
> Probably. I'll give it a try.
>
> I have to find a way to unlock the flash at some point, though. Is it
> okay if I add code to physmap to iterate over the partitions and unlock
> the writable ones if info->mtd->unlock is non-null? Or is there a
> better way to do it?
I'm coming to the conclusion that if there are flash chips which inherit
the Intel insanity of automatically locking themselves on every power
cycle, thus rendering the 'locked' status meaningless, we should just
automatically unlock the whole chip at boot time, from the _chip_
driver.
That way, we can remove that hack from the board drivers which are
currently doing it.
> (btw, I got an "awaiting moderator approval" message from the linux-mtd
> mailer because "Message has a suspicious header". Can someone tell me
> more about this so I can fix my mailer?)
Attachments would do that, but your patches were sensibly inlined.
In fact, your mail got trapped for moderation because you did the
_right_ thing -- you sent them in a thread, with References: headers to
keep them together. But because that means you have References: and no
'Re:' in the Subject: header, that's indistinguishable from the muppets
who try to start a new thread by replying to an existing mail and
changing the subject. So it's trapped for moderation and I get to look
at it and manually approve it.
--
dwmw2
next prev parent reply other threads:[~2006-09-15 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 14:29 [-mm patch 0/4] AVR32 MTD: Introduction Haavard Skinnemoen
2006-09-14 14:30 ` [-mm patch 1/4] AVR32 MTD: Static Memory Controller driver Haavard Skinnemoen
2006-09-14 14:31 ` [-mm patch 2/4] AVR32 MTD: Define struct flash_platform_data Haavard Skinnemoen
2006-09-14 14:32 ` [-mm patch 3/4] AVR32 MTD: Mapping driver for the ATSTK1000 board Haavard Skinnemoen
2006-09-14 14:34 ` [-mm patch 4/4] AVR32 MTD: AT49BV6416 platform device for atstk1000 Haavard Skinnemoen
2006-09-14 20:11 ` [-mm patch 3/4] AVR32 MTD: Mapping driver for the ATSTK1000 board David Woodhouse
2006-09-15 7:56 ` [-mm patch 3/4] AVR32 MTD: Mapping driver for the ATSTK1000board Haavard Skinnemoen
2006-09-15 8:00 ` David Woodhouse [this message]
2006-09-15 8:22 ` [-mm patch 3/4] AVR32 MTD: Mapping driver for theATSTK1000board Haavard Skinnemoen
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=1158307230.24527.36.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=hskinnemoen@atmel.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
all inboxes | Powered by JetHome®