From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
Rusty trivial patch monkey Russell <trivial@rustcorp.com.au>,
Andrew Morton <akpm@zip.com.au>
Subject: Too many __s in donauboe.h
Date: Mon, 4 Oct 2004 14:01:09 +0200 [thread overview]
Message-ID: <20041004120109.GA25380@elf.ucw.cz> (raw)
Hi!
donauboe.h is kernel code, therefore it does not need __s. Please
apply,
Pavel
Index: linux/drivers/net/irda/donauboe.h
===================================================================
--- linux.orig/drivers/net/irda/donauboe.h 2004-10-01 12:24:25.000000000 +0200
+++ linux/drivers/net/irda/donauboe.h 2004-08-19 12:21:14.000000000 +0200
@@ -268,12 +268,11 @@
struct OboeSlot
{
- __u16 len; /*Tweleve bits of packet length */
- __u8 unused;
- __u8 control; /*Slot control/status see below */
- __u32 address; /*Slot buffer address */
-}
-__attribute__ ((packed));
+ u16 len; /*Tweleve bits of packet length */
+ u8 unused;
+ u8 control; /*Slot control/status see below */
+ u32 address; /*Slot buffer address */
+} __attribute__ ((packed));
#define OBOE_NTASKS OBOE_TXRING_OFFSET_IN_SLOTS
@@ -316,7 +315,7 @@
chipio_t io; /* IrDA controller information */
struct qos_info qos; /* QoS capabilities for this device */
- __u32 flags; /* Interface flags */
+ u32 flags; /* Interface flags */
struct pci_dev *pdev; /*PCI device */
int base; /*IO base */
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next reply other threads:[~2004-10-04 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 12:01 Pavel Machek [this message]
2004-10-04 13:43 ` Too many __s in donauboe.h Paul Jackson
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=20041004120109.GA25380@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
/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