From: Tyrel Datwyler <tyreld@linux.ibm.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: james.bottomley@hansenpartnership.com,
linux-scsi@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, brking@linux.ibm.com
Subject: Re: [PATCH] ibmvfc: add new fields for version 2 of several MADs
Date: Tue, 27 Oct 2020 14:52:09 -0700 [thread overview]
Message-ID: <c94f0f87-1863-9c0a-3561-4cbc9330e011@linux.ibm.com> (raw)
In-Reply-To: <yq1v9ew4ekf.fsf@ca-mkp.ca.oracle.com>
On 10/26/20 6:56 PM, Martin K. Petersen wrote:
>
> Tyrel,
>
>> Introduce a targetWWPN field to several MADs. Its possible that a scsi
>> ID of a target can change due to some fabric changes. The WWPN of the
>> scsi target provides a better way to identify the target. Also, add
>> flags for receiving MAD versioning information and advertising client
>> support for targetWWPN with the VIOS. This latter capability flag will
>> be required for future clients capable of requesting multiple hardware
>> queues from the host adapter.
>
> Applied to 5.11/scsi-staging, thanks!
>
Hi Martin,
I'm going to have to ask that this patch be unstaged.
After some clarification from our VIOS folks I made the assumption that the MAD
size was staying the same and new fields just used up existing reserved padding.
Turns out they chose to keep the same amount of padding increasing the size of
those structures. So, this patch needs to be reworked.
Sorry about that,
-Tyrel
next prev parent reply other threads:[~2020-10-27 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 1:36 Tyrel Datwyler
2020-10-27 1:56 ` Martin K. Petersen
2020-10-27 21:52 ` Tyrel Datwyler [this message]
2020-10-30 1:57 ` Martin K. Petersen
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=c94f0f87-1863-9c0a-3561-4cbc9330e011@linux.ibm.com \
--to=tyreld@linux.ibm.com \
--cc=brking@linux.ibm.com \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=martin.petersen@oracle.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®