public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jesse.barnes@intel.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pci: proc.c sparse endian annotations
Date: Tue, 22 Jul 2008 15:18:10 -0700	[thread overview]
Message-ID: <200807221518.10989.jesse.barnes@intel.com> (raw)
In-Reply-To: <1216762847.13328.19.camel@brick>

On Tuesday, July 22, 2008 2:40 pm Harvey Harrison wrote:
> drivers/pci/proc.c:91:3: warning: cast from restricted __le16
> drivers/pci/proc.c:100:3: warning: cast from restricted __le32
> drivers/pci/proc.c:109:3: warning: cast from restricted __le16
> drivers/pci/proc.c:161:40: warning: cast to restricted __le16
> drivers/pci/proc.c:170:41: warning: cast to restricted __le32
> drivers/pci/proc.c:179:40: warning: cast to restricted __le16
>
> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>

Silly me.  I thought it was your mailer corrupting things but of course it was 
the Exchange server for my @intel.com address.  I have no idea why Exchange 
finds text so difficult to handle text without molesting it, but there you 
go.  I'll grab your patch from my lkml mailbox, which necessarily gets routed 
to my virtuousgeek.org addr.

Thanks,
Jesse

  reply	other threads:[~2008-07-22 22:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 22:57 [PATCH] pci: proc.c sparse endian annotations Harvey Harrison
2008-07-22 21:37 ` Jesse Barnes
2008-07-22 21:40   ` Harvey Harrison
2008-07-22 22:18     ` Jesse Barnes [this message]
2008-07-22 22:20     ` Jesse Barnes

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=200807221518.10989.jesse.barnes@intel.com \
    --to=jesse.barnes@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=harvey.harrison@gmail.com \
    --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