From: Sumit Saxena <sumit.saxena@broadcom.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Maurizio Lombardi <mlombard@redhat.com>
Cc: sumit.saxena@avagotech.com, kashyap.desai@avagotech.com,
uday.lingala@avagotech.com, linux-scsi@vger.kernel.org,
jbottomley@parallels.com, thenzl@redhat.com
Subject: RE: [PATCH] megaraid: fix null pointer check in megasas_detach_one().
Date: Wed, 3 Feb 2016 10:12:26 +0530 [thread overview]
Message-ID: <ab1dc36c2043384f7058d05cf19cd16b@mail.gmail.com> (raw)
In-Reply-To: <yq1d1sfop1n.fsf@sermon.lab.mkp.net>
> -----Original Message-----
> From: Martin K. Petersen [mailto:martin.petersen@oracle.com]
> Sent: Tuesday, February 02, 2016 7:24 AM
> To: Maurizio Lombardi
> Cc: sumit.saxena@avagotech.com; kashyap.desai@avagotech.com;
> uday.lingala@avagotech.com; linux-scsi@vger.kernel.org;
> jbottomley@parallels.com; thenzl@redhat.com
> Subject: Re: [PATCH] megaraid: fix null pointer check in
megasas_detach_one().
>
> >>>>> "Maurizio" == Maurizio Lombardi <mlombard@redhat.com> writes:
>
> Maurizio> The pd_seq_sync pointer can't be NULL, we have to check its
> Maurizio> entries instead.
>
> Sumit?
Martin,
Patch looks good but it needs to be rebased with latest repo as very
recently you have checked in few megaraid_sas patches and there are two
critical patches for megaraid_sas are yet pending.
Once we get status of those two outstanding patches, I will ask submitter
to rebase and send this patch again or I will be resending.
Thanks,
Sumit
>
> --
> Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2016-02-03 4:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 12:41 [PATCH] megaraid: fix null pointer check in megasas_detach_one() Maurizio Lombardi
2016-02-02 1:53 ` Martin K. Petersen
2016-02-03 4:42 ` Sumit Saxena [this message]
2016-02-04 2:36 ` Martin K. Petersen
2016-02-05 12:34 ` Sumit Saxena
2016-02-04 15:12 ` Tomas Henzl
2016-02-05 3:24 ` 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=ab1dc36c2043384f7058d05cf19cd16b@mail.gmail.com \
--to=sumit.saxena@broadcom.com \
--cc=jbottomley@parallels.com \
--cc=kashyap.desai@avagotech.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mlombard@redhat.com \
--cc=sumit.saxena@avagotech.com \
--cc=thenzl@redhat.com \
--cc=uday.lingala@avagotech.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.