From: Harvey Harrison <harvey.harrison@gmail.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: ses: fix VPD inquiry overrun
Date: Wed, 30 Jul 2008 10:35:47 -0700 [thread overview]
Message-ID: <1217439347.23389.138.camel@brick> (raw)
In-Reply-To: <48903800.7000008@panasas.com>
On Wed, 2008-07-30 at 12:44 +0300, Boaz Harrosh wrote:
> James Bottomley wrote:
> Harvey where are these bitwise accessors that do an *aligned* access on a
> void pointer. the equivalent of:
> u16 = be16_to_cpup((const __be16 *p)&buff[x]);
> Where I know that x above is some even offset.
>
> I've seen you sent them but I can't find them in my tree
>
They weren't accepted. No need to duplicate be16_to_cpup etc.
Cheers,
Harvey
prev parent reply other threads:[~2008-07-30 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 16:38 ses: fix VPD inquiry overrun James Bottomley
2008-07-30 9:44 ` Boaz Harrosh
2008-07-30 14:53 ` James Bottomley
2008-07-30 17:35 ` Harvey Harrison [this message]
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=1217439347.23389.138.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bharrosh@panasas.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