From: Jan Kasprzak <kas@fi.muni.cz>
To: Arnd Bergmann <arnd@arndb.de>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cosa.h ioctl numbers
Date: Thu, 2 Dec 2004 14:12:25 +0100 [thread overview]
Message-ID: <20041202131224.GI11992@fi.muni.cz> (raw)
In-Reply-To: <200412021358.00844.arnd@arndb.de>
Arnd Bergmann wrote:
: > /* Write the block to the device memory (i.e. download the microcode) */
: > -#define COSAIODOWNLD _IOW('C',0xf2, struct cosa_download)
: > +#define COSAIODOWNLD _IOW('C',0xf2, struct cosa_download *)
:
: Isn't that rather misleading? I suppose the real argument is
: 'struct cosa_download', so you should have some kind of comment there,
: e.g.
:
: #define COSAIODOWNLD _IOW('C',0xf2, long) /* actually struct cosa_download */
Well, the third argument of ioctl(2) is of type
struct cosa_download *.
OK, second try with comments added.
Signed-off-by: Jan "Yenya" Kasprzak <kas@fi.muni.cz>
--- linux-2.6.10-rc2/drivers/net/wan/cosa.h.orig 2004-12-02 13:34:24.142501564 +0100
+++ linux-2.6.10-rc2/drivers/net/wan/cosa.h 2004-12-02 14:09:23.000860524 +0100
@@ -76,10 +76,16 @@
#define COSAIOSTRT _IOW('C',0xf1, int)
/* Read the block from the device memory */
-#define COSAIORMEM _IOWR('C',0xf2, struct cosa_download)
+#define COSAIORMEM _IOWR('C',0xf2, struct cosa_download *)
+ /* actually the struct cosa_download itself; this is to keep
+ * the ioctl number same as in 2.4 in order to keep the user-space
+ * utils compatible. */
/* Write the block to the device memory (i.e. download the microcode) */
-#define COSAIODOWNLD _IOW('C',0xf2, struct cosa_download)
+#define COSAIODOWNLD _IOW('C',0xf2, struct cosa_download *)
+ /* actually the struct cosa_download itself; this is to keep
+ * the ioctl number same as in 2.4 in order to keep the user-space
+ * utils compatible. */
/* Read the device type (one of "srp", "cosa", and "cosa8" for now) */
#define COSAIORTYPE _IOR('C',0xf3, char *)
--
| Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/ Czech Linux Homepage: http://www.linux.cz/ |
> Whatever the Java applications and desktop dances may lead to, Unix will <
> still be pushing the packets around for a quite a while. --Rob Pike <
next prev parent reply other threads:[~2004-12-02 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 12:44 [PATCH] cosa.h ioctl numbers Jan Kasprzak
2004-12-02 12:58 ` Arnd Bergmann
2004-12-02 13:12 ` Jan Kasprzak [this message]
2004-12-02 13:57 ` Andreas Schwab
2004-12-02 14:11 ` Jan Kasprzak
2004-12-02 15:13 ` Andreas Schwab
2004-12-02 15:50 ` Linus Torvalds
2005-01-06 10:02 ` Jan Kasprzak
2004-12-02 15:56 ` Jan Kasprzak
2004-12-02 16:45 ` Andreas Schwab
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=20041202131224.GI11992@fi.muni.cz \
--to=kas@fi.muni.cz \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 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.