From: Kevin Wolf <kwolf@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] slirp: kill ugly macros
Date: Thu, 16 Feb 2012 12:17:12 +0100 [thread overview]
Message-ID: <4F3CE5B8.8050107@redhat.com> (raw)
In-Reply-To: <CAFEAcA_CWR-Pkr30pKa0+8f5hwMCDbMFm84gc6jvMbKvQQt8+g@mail.gmail.com>
Am 16.02.2012 12:09, schrieb Peter Maydell:
> On 16 February 2012 11:06, Kevin Wolf <kwolf@redhat.com> wrote:
>> What are all these m_ and mh_ prefixes for struct fields even about?
>> When I have an mbuf, I know perfectly well that it is one, and that
>> m_hdr is a header of it.
>
> That's the dead hand of Sixth Edition Unix and its C compiler
> that put all struct fields in a single namespace...
Oh, fun. Things you never wanted to know... ;-)
Kevin
next prev parent reply other threads:[~2012-02-16 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 18:45 [Qemu-devel] [PATCH] slirp: kill ugly macros Michael S. Tsirkin
2012-02-15 18:55 ` Jan Kiszka
2012-02-16 11:06 ` Kevin Wolf
2012-02-16 11:09 ` Peter Maydell
2012-02-16 11:17 ` Kevin Wolf [this message]
2012-02-17 13:32 ` Jan Kiszka
2012-02-16 11:52 ` Michael S. Tsirkin
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=4F3CE5B8.8050107@redhat.com \
--to=kwolf@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).