From: Dan Carpenter <dan.carpenter@oracle.com>
To: James Smart <jsmart2021@gmail.com>
Cc: axboe@kernel.dk, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, jejb@linux.ibm.com,
kernel-janitors@vger.kernel.org, linux-nvme@lists.infradead.org,
hch@infradead.org, paul.ely@broadcom.com, hare@suse.de
Subject: Re: [PATCH 0/3] lpfc: Fix errors in LS receive refactoring
Date: Fri, 22 May 2020 07:29:11 +0000 [thread overview]
Message-ID: <20200522072911.GA22511@kadam> (raw)
In-Reply-To: <20200520185929.48779-1-jsmart2021@gmail.com>
On Wed, May 20, 2020 at 11:59:26AM -0700, James Smart wrote:
> A prior patch set refactored lpfc to create common routines for NVME LS
> handling for use by both the initiator and target paths. The refactoring
> introduced several errors spotted by additional testing and static checker
> reporting.
>
> This patch set corrects those errors.
>
> The patches should enter via the nvme tree, as the lpfc modifications were
> in support of nvme-fc transport api deltas merged via the nvme tree.
>
> -- james
Thanks!
Reviewed-by: Dan Carpenter <dan.carpenter@oracle.com>
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: James Smart <jsmart2021@gmail.com>
Cc: axboe@kernel.dk, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, jejb@linux.ibm.com,
kernel-janitors@vger.kernel.org, linux-nvme@lists.infradead.org,
hch@infradead.org, paul.ely@broadcom.com, hare@suse.de
Subject: Re: [PATCH 0/3] lpfc: Fix errors in LS receive refactoring
Date: Fri, 22 May 2020 10:29:11 +0300 [thread overview]
Message-ID: <20200522072911.GA22511@kadam> (raw)
In-Reply-To: <20200520185929.48779-1-jsmart2021@gmail.com>
On Wed, May 20, 2020 at 11:59:26AM -0700, James Smart wrote:
> A prior patch set refactored lpfc to create common routines for NVME LS
> handling for use by both the initiator and target paths. The refactoring
> introduced several errors spotted by additional testing and static checker
> reporting.
>
> This patch set corrects those errors.
>
> The patches should enter via the nvme tree, as the lpfc modifications were
> in support of nvme-fc transport api deltas merged via the nvme tree.
>
> -- james
Thanks!
Reviewed-by: Dan Carpenter <dan.carpenter@oracle.com>
regards,
dan carpenter
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: James Smart <jsmart2021@gmail.com>
Cc: linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org,
kernel-janitors@vger.kernel.org, paul.ely@broadcom.com,
hare@suse.de, jejb@linux.ibm.com, axboe@kernel.dk,
martin.petersen@oracle.com, hch@infradead.org
Subject: Re: [PATCH 0/3] lpfc: Fix errors in LS receive refactoring
Date: Fri, 22 May 2020 10:29:11 +0300 [thread overview]
Message-ID: <20200522072911.GA22511@kadam> (raw)
In-Reply-To: <20200520185929.48779-1-jsmart2021@gmail.com>
On Wed, May 20, 2020 at 11:59:26AM -0700, James Smart wrote:
> A prior patch set refactored lpfc to create common routines for NVME LS
> handling for use by both the initiator and target paths. The refactoring
> introduced several errors spotted by additional testing and static checker
> reporting.
>
> This patch set corrects those errors.
>
> The patches should enter via the nvme tree, as the lpfc modifications were
> in support of nvme-fc transport api deltas merged via the nvme tree.
>
> -- james
Thanks!
Reviewed-by: Dan Carpenter <dan.carpenter@oracle.com>
regards,
dan carpenter
next prev parent reply other threads:[~2020-05-22 7:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 18:59 [PATCH 0/3] lpfc: Fix errors in LS receive refactoring James Smart
2020-05-20 18:59 ` James Smart
2020-05-20 18:59 ` James Smart
2020-05-20 18:59 ` [PATCH 1/3] lpfc: Fix pointer checks and comments " James Smart
2020-05-20 18:59 ` James Smart
2020-05-20 18:59 ` James Smart
2020-05-20 18:59 ` [PATCH 2/3] lpfc: fix axchg pointer reference after free and double frees James Smart
2020-05-20 18:59 ` James Smart
2020-05-20 18:59 ` James Smart
2020-05-20 18:59 ` [PATCH 3/3] lpfc: Fix return value in __lpfc_nvme_ls_abort James Smart
2020-05-20 18:59 ` James Smart
2020-05-20 18:59 ` James Smart
2020-05-22 7:29 ` Dan Carpenter [this message]
2020-05-22 7:29 ` [PATCH 0/3] lpfc: Fix errors in LS receive refactoring Dan Carpenter
2020-05-22 7:29 ` Dan Carpenter
2020-05-26 14:53 ` Christoph Hellwig
2020-05-26 14:53 ` Christoph Hellwig
2020-05-26 14:53 ` Christoph Hellwig
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=20200522072911.GA22511@kadam \
--to=dan.carpenter@oracle.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jejb@linux.ibm.com \
--cc=jsmart2021@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=paul.ely@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.