From: Stefano Brivio <sbrivio@redhat.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Dick Kennedy <dick.kennedy@broadcom.com>,
James Smart <james.smart@broadcom.com>,
QLogic-Storage-Upstream@cavium.com,
Maurizio Lombardi <mlombard@redhat.com>,
martin.petersen@oracle.com,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] lpfc: Don't return internal MBXERR_ERROR code from probe function
Date: Wed, 6 Sep 2017 10:47:38 +0200 [thread overview]
Message-ID: <20170906104738.50b81cd5@elisabeth> (raw)
In-Reply-To: <20170906084235.n22ll6z7pnvi6t3q@linux-x5ow.site>
On Wed, 6 Sep 2017 10:42:35 +0200
Johannes Thumshirn <jthumshirn@suse.de> wrote:
> On Wed, Sep 06, 2017 at 10:32:22AM +0200, Stefano Brivio wrote:
> >
> > I didn't get feedback about this patch. Is there any issue with the
> > submission?
> >
> > I think it actually fixes a quite critical issue, if initialization
> > fails we have crashes on reboot like the one reported below [1], and
> > should perhaps also be queued for -stable.
>
> It seems to have slipped trough the cracks, can you please re-submit?
The original submission is archived at
https://marc.info/?l=linux-scsi&m=150392554622786&w=2. Before I cause
any confusion... do you want me to re-submit this with the same
subject? As v2 with a comment?
--
Stefano
next prev parent reply other threads:[~2017-09-06 8:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 13:05 [PATCH] lpfc: Don't return internal MBXERR_ERROR code from probe function Stefano Brivio
2017-09-06 8:32 ` Stefano Brivio
2017-09-06 8:42 ` Johannes Thumshirn
2017-09-06 8:47 ` Stefano Brivio [this message]
2017-09-06 8:52 ` Johannes Thumshirn
2017-09-06 9:02 ` [PATCH RESEND] " Stefano Brivio
2017-09-06 9:30 ` Johannes Thumshirn
2017-09-06 9:54 ` Stefano Brivio
2017-09-06 10:02 ` Johannes Thumshirn
2017-09-15 1:19 ` Martin K. Petersen
2017-09-15 14:18 ` James Smart
2017-09-16 1:16 ` 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=20170906104738.50b81cd5@elisabeth \
--to=sbrivio@redhat.com \
--cc=QLogic-Storage-Upstream@cavium.com \
--cc=dick.kennedy@broadcom.com \
--cc=james.smart@broadcom.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mlombard@redhat.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.