From: Matthew Wilcox <matthew@wil.cx>
To: mike.miller@hp.com
Cc: akpm@osdl.org, axboe@suse.de, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] cciss 2.6: pci domain info
Date: Fri, 17 Jun 2005 20:35:17 +0100 [thread overview]
Message-ID: <20050617193517.GN11655@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050617183124.GA9913@beardog.cca.cpqcorp.net>
On Fri, Jun 17, 2005 at 01:31:24PM -0500, mike.miller@hp.com wrote:
> This patch adds pci domain info to our CCISS_GETPCIINFO ioctl. This
> is to support the next generation of Itanium platforms. We had a couple
> of spare bytes in the structure. Impact to existing apps should be
> minimal. Please consider this patch for inclusion.
> typedef struct _cciss_pci_info_struct
> {
> + unsigned int domain;
> unsigned char bus;
> unsigned char dev_fn;
> __u32 board_id;
Um, what? There's no way this doesn't break the ABI. You do have spare
bytes in the struct, but to use them, you have to add an 'unsigned short'
between dev_fn and board_id:
typedef struct _cciss_pci_info_struct
{
unsigned char bus;
unsigned char dev_fn;
+ unsigned int domain;
__u32 board_id;
}
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2005-06-17 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 18:31 mike.miller
2005-06-17 19:34 ` Christoph Hellwig
2005-06-17 19:35 ` Matthew Wilcox [this message]
2005-06-17 19:40 Miller, Mike (OS Dev)
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=20050617193517.GN11655@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mike.miller@hp.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
all inboxes | Powered by JetHome®