linux-kernel - [PATCH] IDE: typedef struct clean-up

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 16 Oct 2006 07:00:42 -0600 (MDT)
From:	vegard@...tkore.net
To:	linux-kernel@...r.kernel.org
Cc:	"Bartlomiej Zolnierkiewicz" <B.Zolnierkiewicz@...a.pw.edu.pl>,
	"Jens Axboe" <axboe@...nel.dk>,
	"Paul Bristow" <paul@...lbristow.net>,
	"Gadi Oxman" <gadio@...vision.net.il>
Subject: [PATCH] IDE: typedef struct clean-up

From: Vegard Nossum <vegard@...tkore.net>

Replaces typedefs with struct-constructs for large parts of the IDE API
and drivers. No semantic changes. Rationale: CodingStyle, chapter 5.

Signed-off-by: Vegard Nossum <vegard@...tkore.net>
---

Applies to Linus's 2.6 tree.

I figured that this kind of easy/routine job would make for a gentle
introduction to kernel programming. However, what is the general opinion
of this kind of work, should it be done or not? (I realize that I may be
challenging some established habits with these changes.)

Also, what are the rules for enum and function-pointer typedefs?
CodingStyle does not discuss these cases.

Complete patch is 376K and follows as a link. This violates point 6 of
SubmittingPatches (no links), but is justified by point 7 (e-mail size).

http://peltkore.net/~vegard/linux-2.6-ide-typedef-vegard.patch

Regards from Vegard's

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/