From: Greg KH <greg@kroah.com>
To: Arvydas Sidorenko <asido4@gmail.com>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] drivers/staging/crystalhd/: cleanup typedefs
Date: Mon, 12 Sep 2011 16:50:17 +0200 [thread overview]
Message-ID: <20110912145017.GB25347@kroah.com> (raw)
In-Reply-To: <1315500369-11204-2-git-send-email-asido4@gmail.com>
On Thu, Sep 08, 2011 at 06:46:09PM +0200, Arvydas Sidorenko wrote:
> Cleans the typedef declarations in bc_dts_types.h file. Most of them aren't
> used. The ones are used are 'uint32_t' and similar ones, but I don't see the
> point of them since they are declared in stdint.h, unless some sort of embeded
> systems don't have it (no experience with it).
> So simply removing them doesn't cause any compilation errors or warnings on
> my laptop.
>
> Signed-off-by: Arvydas Sidorenko <asido4@gmail.com>
> ---
> drivers/staging/crystalhd/bc_dts_types.h | 41 +-----------------------------
> 1 files changed, 1 insertions(+), 40 deletions(-)
>
> diff --git a/drivers/staging/crystalhd/bc_dts_types.h b/drivers/staging/crystalhd/bc_dts_types.h
> index d2131e7..42d7cfd 100644
> --- a/drivers/staging/crystalhd/bc_dts_types.h
> +++ b/drivers/staging/crystalhd/bc_dts_types.h
> @@ -29,29 +29,8 @@
> #include <stdint.h>
> #endif
>
> -#ifndef PVOID
> -typedef void *PVOID;
> -#endif
> -
> -#ifndef BOOL
> -typedef int BOOL;
> -#endif
> -
> #if defined(__KERNEL__) || defined(__LINUX_USER__)
>
> -#ifdef __LINUX_USER__ /* Don't include these for KERNEL */
> -typedef uint32_t ULONG;
> -typedef int32_t LONG;
> -typedef void *HANDLE;
> -#ifndef VOID
> -typedef void VOID;
> -#endif
> -typedef void *LPVOID;
> -typedef uint32_t DWORD;
> -typedef uint32_t UINT32;
> -typedef uint32_t *LPDWORD;
> -typedef unsigned char *PUCHAR;
> -
> #ifndef TRUE
> #define TRUE 1
> #endif
You can drop this too, right?
> @@ -70,28 +49,10 @@ typedef unsigned char *PUCHAR;
> #else
>
> #ifndef uint64_t
> -typedef struct _uint64_t {
> +struct _uint64_t {
> uint32_t low_dw;
> uint32_t hi_dw;
> } uint64_t;
> #endif
This whole thing should also be removed.
Care to redo this?
greg k-h
parent reply other threads:[~2011-09-12 14:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1315500369-11204-2-git-send-email-asido4@gmail.com>]
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=20110912145017.GB25347@kroah.com \
--to=greg@kroah.com \
--cc=asido4@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®