From: Paul Bolle <pebolle@tiscali.nl>
To: Hannes Reinecke <hare@suse.de>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
Gleb Natapov <gleb@redhat.com>,
linux-kernel@vger.kernel.org,
Johannes Thumshirn <jtumshirn@suse.com>
Subject: Re: [PATCH] edd: support original Phoenix EDD 3.0 information
Date: Thu, 21 May 2015 09:23:15 +0200 [thread overview]
Message-ID: <1432192995.21715.108.camel@x220> (raw)
In-Reply-To: <1432192728-51789-1-git-send-email-hare@suse.de>
On Thu, 2015-05-21 at 09:18 +0200, Hannes Reinecke wrote:
> - /* We support only T13 spec */
> - if (info->params.device_path_info_length != 44)
> + /* We support T13 d1572 and the original Phoenix spec */
> + if (info->params.device_path_info_length != 44 &&
> + info->params.device_path_info_lenght != 36)
Did this compile?
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-05-21 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 7:18 [PATCH] edd: support original Phoenix EDD 3.0 information Hannes Reinecke
2015-05-21 7:23 ` Paul Bolle [this message]
2015-05-21 7:31 ` Hannes Reinecke
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=1432192995.21715.108.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=gleb@redhat.com \
--cc=hare@suse.de \
--cc=hpa@linux.intel.com \
--cc=jtumshirn@suse.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