From: Chaitra Basappa <chaitra.basappa@broadcom.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Joe Lawrence <joe.lawrence@stratus.com>
Cc: Sathya Prakash Veerichetty <sathya.prakash@broadcom.com>,
emilne@redhat.com, linux-scsi@vger.kernel.org,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
Calvin Owens <calvinowens@fb.com>
Subject: RE: [PATCH] mpt3sas - remove unused fw_event_work delayed_work
Date: Fri, 15 Apr 2016 15:27:46 +0530 [thread overview]
Message-ID: <649a6feca5fbc7e60aafd7d5e59e1edc@mail.gmail.com> (raw)
In-Reply-To: <yq1r3e7sibv.fsf@sermon.lab.mkp.net>
Joe ,
The below mentioned patch is an older patch, verified latest code also
the code before merging(mpt2sas & mpt3sas) didn't find changes of below
patch. So I am searching for the patch which has removed the
functionality/changes of the below patch.
I shall get back to you on this by Monday.
Thanks,
Chaitra
-----Original Message-----
From: Martin K. Petersen [mailto:martin.petersen@oracle.com]
Sent: Friday, April 15, 2016 8:13 AM
To: Joe Lawrence
Cc: Chaitra Basappa; Sathya Prakash Veerichetty; emilne@redhat.com;
linux-scsi@vger.kernel.org; Suganath Prabu Subramani; Calvin Owens
Subject: Re: [PATCH] mpt3sas - remove unused fw_event_work delayed_work
>>>>> "Joe" == Joe Lawrence <joe.lawrence@stratus.com> writes:
Joe> Do we know why f1c35e6aea579 "mpt2sas: RESCAN Barrier work is added
Joe> in case of HBA reset" was unneeded for the mpt3 version? If that
Joe> is interesting, that info could be added to v2 commit message as
Joe> well.
Chaitra?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2016-04-15 9:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 17:56 [PATCH] mpt3sas - remove unused fw_event_work delayed_work Joe Lawrence
2016-04-01 18:04 ` Laurence Oberman
2016-04-01 18:51 ` Ewan D. Milne
2016-04-01 19:13 ` Joe Lawrence
2016-04-01 20:04 ` Ewan D. Milne
2016-04-01 20:14 ` Sathya Prakash
2016-04-11 11:13 ` Chaitra Basappa
2016-04-11 12:08 ` Joe Lawrence
2016-04-15 2:43 ` Martin K. Petersen
2016-04-15 9:57 ` Chaitra Basappa [this message]
2016-04-15 17:26 ` Sathya Prakash Veerichetty
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=649a6feca5fbc7e60aafd7d5e59e1edc@mail.gmail.com \
--to=chaitra.basappa@broadcom.com \
--cc=calvinowens@fb.com \
--cc=emilne@redhat.com \
--cc=joe.lawrence@stratus.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sathya.prakash@broadcom.com \
--cc=suganath-prabu.subramani@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.