From: David Woodhouse <dwmw2@infradead.org>
To: Eric <ebrower@usa.net>
Cc: Tim Hockin <thockin@sun.com>, MTD List <linux-mtd@lists.infradead.org>
Subject: Re: [Re: [structure field names] ]
Date: Sat, 21 Jul 2001 13:01:26 +0100 [thread overview]
Message-ID: <30757.995716886@redhat.com> (raw)
In-Reply-To: <20010720173422.18538.qmail@nwcst284.netaddress.usa.net>
ebrower@usa.net said:
> In the case of the MEMREADOOB and MEMWRITEOOB ioctls, we still must
> do conversions so that the u8* is understood by the kernel to be a
> 32-bit userspace pointer and not a 64-bit kernelspace pointer.
I don't like the MEMREADOOB and MEMWRITEOOB ioctls very much. I'm severely
tempted to deprecate them and have a separate device for OOB space access.
Does anyone ever actually use the /dev/mtdr<n> read-only devices?
> I only brought this up because if the structure member names are
> modified, they must be modified in the sparc64 patch as well. This
> is, unfortunately, a required headache.
I am sympathetic to Tim's request, but at this stage I think the pain of
changing names probably outweighs the benefit.
--
dwmw2
next prev parent reply other threads:[~2001-07-21 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-20 17:34 [Re: [structure field names] ] Eric
2001-07-21 12:01 ` David Woodhouse [this message]
2001-07-23 17:43 ` Tim Hockin
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=30757.995716886@redhat.com \
--to=dwmw2@infradead.org \
--cc=ebrower@usa.net \
--cc=linux-mtd@lists.infradead.org \
--cc=thockin@sun.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.