From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: akpm@linux-foundation.org
Cc: linux-scsi@vger.kernel.org, harvey.harrison@gmail.com
Subject: Re: [patch 13/17] scsi: remove private implementation of get_unaligned_be32
Date: Wed, 29 Oct 2008 16:48:14 -0500 [thread overview]
Message-ID: <1225316894.3257.19.camel@localhost.localdomain> (raw)
In-Reply-To: <200810292124.m9TLOjl1021276@imap1.linux-foundation.org>
On Wed, 2008-10-29 at 14:24 -0700, akpm@linux-foundation.org wrote:
> From: Harvey Harrison <harvey.harrison@gmail.com>
>
> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/scsi/libsas/sas_expander.c | 9 +++++----
> include/scsi/scsi.h | 6 ------
> 2 files changed, 5 insertions(+), 10 deletions(-)
>
> diff -puN drivers/scsi/libsas/sas_expander.c~scsi-remove-private-implementation-of-get_unaligned_be32 drivers/scsi/libsas/sas_expander.c
> --- a/drivers/scsi/libsas/sas_expander.c~scsi-remove-private-implementation-of-get_unaligned_be32
> +++ a/drivers/scsi/libsas/sas_expander.c
> @@ -24,6 +24,7 @@
>
> #include <linux/scatterlist.h>
> #include <linux/blkdev.h>
> +#include <asm/unaligned.h>
>
> #include "sas_internal.h"
>
> @@ -541,10 +542,10 @@ int sas_smp_get_phy_events(struct sas_ph
> if (!res)
> goto out;
>
> - phy->invalid_dword_count = scsi_to_u32(&resp[12]);
> - phy->running_disparity_error_count = scsi_to_u32(&resp[16]);
> - phy->loss_of_dword_sync_count = scsi_to_u32(&resp[20]);
> - phy->phy_reset_problem_count = scsi_to_u32(&resp[24]);
> + phy->invalid_dword_count = get_unaligned_be32(&resp[12]);
> + phy->running_disparity_error_count = get_unaligned_be32(&resp[16]);
> + phy->loss_of_dword_sync_count = get_unaligned_be32(&resp[20]);
> + phy->phy_reset_problem_count = get_unaligned_be32(&resp[24]);
>
> out:
> kfree(resp);
> diff -puN include/scsi/scsi.h~scsi-remove-private-implementation-of-get_unaligned_be32 include/scsi/scsi.h
> --- a/include/scsi/scsi.h~scsi-remove-private-implementation-of-get_unaligned_be32
> +++ a/include/scsi/scsi.h
> @@ -527,10 +527,4 @@ static inline void set_driver_byte(struc
> /* Used to obtain the PCI location of a device */
> #define SCSI_IOCTL_GET_PCI 0x5387
>
> -/* Pull a u32 out of a SCSI message (using BE SCSI conventions) */
> -static inline __u32 scsi_to_u32(__u8 *ptr)
> -{
> - return (ptr[0]<<24) + (ptr[1]<<16) + (ptr[2]<<8) + ptr[3];
> -}
> -
> #endif /* _SCSI_SCSI_H */
No ... as I've said several times now, there's a debate going on about
what we're supposed to be doing with all of this (either putting it in
SCSI, pulling it out or just using the inline notation. I'm not putting
a patch like this in until we at least get some consensus.
James
next prev parent reply other threads:[~2008-10-29 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 21:24 [patch 13/17] scsi: remove private implementation of get_unaligned_be32 akpm
2008-10-29 21:48 ` James Bottomley [this message]
2008-10-29 22:07 ` Andrew Morton
2008-10-29 22:13 ` James Bottomley
2008-10-29 22:29 ` Harvey Harrison
2008-10-30 1:03 ` Harvey Harrison
2008-10-30 14:17 ` James Bottomley
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=1225316894.3257.19.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=linux-scsi@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