qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: Juan Quintela <quintela@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	Markus Armbruster <armbru@redhat.com>,
	qemu list <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] Re: [PATCH 4/5] atapi: GESN: Add enums for commonly-used field types
Date: Fri, 08 Apr 2011 16:21:38 +0200	[thread overview]
Message-ID: <4D9F19F2.3060705@redhat.com> (raw)
In-Reply-To: <d5b9ec36fb3b1958f3034787d279b20ab221ae4c.1302246567.git.amit.shah@redhat.com>

Am 08.04.2011 09:15, schrieb Amit Shah:
> Instead of using magic numbers, use enums that are more descriptive of
> the fields being used.
> 
> Signed-off-by: Amit Shah <amit.shah@redhat.com>
> ---
>  hw/ide/core.c |   11 +++++++++--
>  1 files changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/ide/core.c b/hw/ide/core.c
> index 730587e..cdc2c56 100644
> --- a/hw/ide/core.c
> +++ b/hw/ide/core.c
> @@ -1118,12 +1118,19 @@ static void handle_get_event_status_notification(IDEState *s,
>                                                   uint8_t *buf,
>                                                   const uint8_t *packet)
>  {
> +    enum cdb {
> +        polled = 1,
> +        request = 4,
> +        allocation_length_msb = 7,
> +        allocation_length_lsb = 8,
> +        control = 9,
> +    };

Wouldn't it be nicer to make this a struct and just cast packet to a
pointer to this struct? At first I didn't realize that this should be
field offsets and I find something like packet + allocation_length_msb
rather confusing.

Kevin

  reply	other threads:[~2011-04-08 14:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08  7:15 [Qemu-devel] [PATCH 0/5] atapi: Implement 'media' subcommand for GESN Amit Shah
2011-04-08  7:15 ` [Qemu-devel] [PATCH 1/5] atapi: Allow GET_EVENT_STATUS_NOTIFICATION after media change Amit Shah
2011-04-08  7:25   ` [Qemu-devel] " Amit Shah
2011-04-08 10:54   ` [Qemu-devel] " Markus Armbruster
2011-04-08 11:03     ` Kevin Wolf
2011-04-08  7:15 ` [Qemu-devel] [PATCH 2/5] ide: Move GET_EVENT_STATUS_NOTIFICATION command handling to its own function Amit Shah
2011-04-08  7:15 ` [Qemu-devel] [PATCH 3/5] atapi: GESN: Spin off No Event Available handling into " Amit Shah
2011-04-08 13:31   ` [Qemu-devel] " Kevin Wolf
2011-04-09 10:36     ` Amit Shah
2011-04-11  8:51       ` Kevin Wolf
2011-04-08  7:15 ` [Qemu-devel] [PATCH 4/5] atapi: GESN: Add enums for commonly-used field types Amit Shah
2011-04-08 14:21   ` Kevin Wolf [this message]
2011-04-09 10:43     ` [Qemu-devel] " Amit Shah
2011-04-08  7:15 ` [Qemu-devel] [PATCH 5/5] atapi: Implement 'media' subcommand of GET_EVENT_STATUS_NOTIFICATION command Amit Shah
2011-04-08 16:17   ` [Qemu-devel] " Kevin Wolf
2011-04-09 13:57     ` Amit Shah
2011-04-08  7:21 ` [Qemu-devel] Re: [PATCH 0/5] atapi: Implement 'media' subcommand for GESN Paolo Bonzini
2011-04-08  9:39 ` [Qemu-devel] " Markus Armbruster
2011-04-11  6:18   ` Amit Shah
2011-04-11 13:46     ` Markus Armbruster
2011-04-12  4:22       ` Amit Shah

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=4D9F19F2.3060705@redhat.com \
    --to=kwolf@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).