From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 5/12] ide: remove task_ioreg_t typedef
Date: Wed, 17 Oct 2007 21:47:00 +0400 [thread overview]
Message-ID: <47164A94.1070502@ru.mvista.com> (raw)
In-Reply-To: <200710082310.04079.bzolnier@gmail.com>
Bartlomiej Zolnierkiewicz wrote:
> Remove task_ioreg_t typedef from the kernel code (but leave it
> in <linux/hdreg.h> for #ifndef/#endif __KERNEL__ case).
> While at it also move sata_ioreg_t typedef under #ifndef/#endif __KERNEL__.
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Acked-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> Index: b/include/linux/hdreg.h
> ===================================================================
> --- a/include/linux/hdreg.h
> +++ b/include/linux/hdreg.h
[...]
> @@ -116,8 +116,8 @@ typedef union ide_reg_valid_s {
> } ide_reg_valid_t;
>
> typedef struct ide_task_request_s {
> - task_ioreg_t io_ports[8];
> - task_ioreg_t hob_ports[8];
> + __u8 io_ports[8];
> + __u8 hob_ports[8];
> ide_reg_valid_t out_flags;
> ide_reg_valid_t in_flags;
> int data_phase;
> @@ -133,32 +133,32 @@ typedef struct ide_ioctl_request_s {
> } ide_ioctl_request_t;
>
> struct hd_drive_cmd_hdr {
> - task_ioreg_t command;
> - task_ioreg_t sector_number;
> - task_ioreg_t feature;
> - task_ioreg_t sector_count;
> + __u8 command;
> + __u8 sector_number;
> + __u8 feature;
> + __u8 sector_count;
> };
>
> typedef struct hd_drive_task_hdr {
> - task_ioreg_t data;
> - task_ioreg_t feature;
> - task_ioreg_t sector_count;
> - task_ioreg_t sector_number;
> - task_ioreg_t low_cylinder;
> - task_ioreg_t high_cylinder;
> - task_ioreg_t device_head;
> - task_ioreg_t command;
> + __u8 data;
> + __u8 feature;
> + __u8 sector_count;
> + __u8 sector_number;
> + __u8 low_cylinder;
> + __u8 high_cylinder;
> + __u8 device_head;
> + __u8 command;
> } task_struct_t;
>
> typedef struct hd_drive_hob_hdr {
> - task_ioreg_t data;
> - task_ioreg_t feature;
> - task_ioreg_t sector_count;
> - task_ioreg_t sector_number;
> - task_ioreg_t low_cylinder;
> - task_ioreg_t high_cylinder;
> - task_ioreg_t device_head;
> - task_ioreg_t control;
> + __u8 data;
> + __u8 feature;
> + __u8 sector_count;
> + __u8 sector_number;
> + __u8 low_cylinder;
> + __u8 high_cylinder;
> + __u8 device_head;
> + __u8 control;
> } hob_struct_t;
Why use __u8 here, and u8 elsewhere?
> #define TASKFILE_INVALID 0x7fff
> Index: b/include/linux/ide.h
> ===================================================================
> --- a/include/linux/ide.h
> +++ b/include/linux/ide.h
> @@ -1017,7 +1017,8 @@ int ide_end_dequeued_request(ide_drive_t
>
> extern void ide_set_handler (ide_drive_t *drive, ide_handler_t *handler, unsigned int timeout, ide_expiry_t *expiry);
>
> -extern void ide_execute_command(ide_drive_t *, task_ioreg_t cmd, ide_handler_t *, unsigned int, ide_expiry_t *);
> +void ide_execute_command(ide_drive_t *, u8 cmd, ide_handler_t *,
> + unsigned int, ide_expiry_t *);
Hm, why name only second parameter? :-|
MBR, Sergei
next prev parent reply other threads:[~2007-10-17 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 21:10 [PATCH 5/12] ide: remove task_ioreg_t typedef Bartlomiej Zolnierkiewicz
2007-10-17 17:47 ` Sergei Shtylyov [this message]
2007-10-24 21:27 ` Bartlomiej Zolnierkiewicz
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=47164A94.1070502@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.com \
--cc=linux-ide@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 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.