From: "H. Peter Anvin" <hpa@zytor.com>
To: Paul Sokolovsky <pmiscml@gmail.com>
Cc: linux-kernel@vger.kernel.org, kernel-discuss@handhelds.org,
Anton Vorontsov <cbou@mail.ru>
Subject: Re: [RFC] Virtual methods for devices and generalized GPIO support using it
Date: Wed, 28 Mar 2007 17:08:57 -0700 [thread overview]
Message-ID: <460B0399.5080904@zytor.com> (raw)
In-Reply-To: <1547009361.20070329025215@gmail.com>
Paul Sokolovsky wrote:
>
> By this criteria I happened to choose macros syntax. But it's still
> merely a syntax, and I don't pledge for it. If there's more movement
> towards using explicit low-level forms like 1) or 2) instead of
> introducing new syntactic pattern, then macro syntax can be considered
> to have fulfilled its introductory role and can be dropped.
>
"Movement towards?!" That's been a fundamental part of Linux design
since the very beginning.
-hpa
prev parent reply other threads:[~2007-03-29 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 8:36 [RFC] Virtual methods for devices and generalized GPIO support using it Paul Sokolovsky
2007-03-28 16:32 ` H. Peter Anvin
2007-03-28 23:52 ` Paul Sokolovsky
2007-03-29 0:08 ` H. Peter Anvin [this message]
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=460B0399.5080904@zytor.com \
--to=hpa@zytor.com \
--cc=cbou@mail.ru \
--cc=kernel-discuss@handhelds.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmiscml@gmail.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