From: Christoph Hellwig <hch@infradead.org>
To: Greg KH <greg@kroah.com>
Cc: Alex Aizman <itn780@yahoo.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE 2/6] Linux-iSCSI High-Performance Initiator
Date: Tue, 12 Apr 2005 08:27:33 +0100 [thread overview]
Message-ID: <20050412072733.GA32354@infradead.org> (raw)
In-Reply-To: <20050412053650.GF32372@kroah.com>
On Mon, Apr 11, 2005 at 10:36:51PM -0700, Greg KH wrote:
> On Mon, Apr 11, 2005 at 08:24:08PM -0700, Alex Aizman wrote:
> > Common header files:
> > - iscsi_ifev.h (user/kernel events).
>
> These structures cross the user/kernel boundry? If so, they _must_ use
> the __u32 and friends types, not the horrible uint32_t mess...
No, C99 are just fine.
next prev parent reply other threads:[~2005-04-12 7:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 3:24 [ANNOUNCE 2/6] Linux-iSCSI High-Performance Initiator Alex Aizman
2005-04-12 5:34 ` Greg KH
2005-04-12 5:35 ` Greg KH
2005-04-12 16:34 ` Dmitry Yusupov
2005-04-12 5:36 ` Greg KH
2005-04-12 7:27 ` Christoph Hellwig [this message]
2005-04-12 7:45 ` Greg KH
2005-04-12 8:14 ` Christoph Hellwig
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=20050412072733.GA32354@infradead.org \
--to=hch@infradead.org \
--cc=greg@kroah.com \
--cc=itn780@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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