linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kashyap Desai <kashyap.desai@avagotech.com>
To: Sumit Saxena <sumit.saxena@avagotech.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, thenzl@redhat.com, hch@infradead.org,
	jbottomley@parallels.com,
	Kiran Kumar Kasturi <kiran-kumar.kasturi@avagotech.com>,
	Uday Lingala <uday.lingala@avagotech.com>
Subject: RE: [PATCH 02/12] megaraid_sas : Code optimization- remove PCI Ids based checks
Date: Wed, 28 Oct 2015 20:00:47 +0530	[thread overview]
Message-ID: <c184826206ec6525b7ecb9e034cb6368@mail.gmail.com> (raw)
In-Reply-To: <8e8133a4c138153187671ddf75181b8b@mail.gmail.com>

>
> > -----Original Message-----
> > From: Martin K. Petersen [mailto:martin.petersen@oracle.com]
> > Sent: Wednesday, October 28, 2015 8:03 AM
> > To: sumit.saxena@avagotech.com
> > Cc: linux-scsi@vger.kernel.org; thenzl@redhat.com;
> > martin.petersen@oracle.com; hch@infradead.org;
> > jbottomley@parallels.com; kashyap.desai@avagotech.com;
> > kiran-kumar.kasturi@avagotech.com;
> > uday.lingala@avagotech.com
> > Subject: Re: [PATCH 02/12] megaraid_sas : Code optimization- remove
> > PCI
> Ids
> > based checks
> >
> > >>>>> "Sumit" == sumit saxena <sumit.saxena@avagotech.com> writes:
> >
> > Sumit> Code optimization: remove PCI id based checks and instead of
> > Sumit> those use instance->ctrl_context to make call whether
> > Sumit> controller is MFI based OR fusion adapter.  fusion adapters
> > Sumit> further are also divided in two categories- 1)THUNDERBOLT
> > Sumit> SERIES and 2)INVADER SERIES.
> >
> > Does not apply against current upstream. Please fix and repost.
>
> Martin, This patch set is not based on current upstream but rebased on top
> of few patches sent by me prior to this patch series. Patches sent prior
> to
> this patch series are not yet accepted.

Martin -

Here is last outstanding patch series.
http://marc.info/?l=linux-scsi&m=144102204225400&w=2

Last patch series was missed because of small rebase issue. James suggested
not to ACK anything which is not critical to avoid such issue and probably
piggy back those patches.
Last series and latest series has reviewed-by tags. Can we have outstanding
patches committed in next window ?

>
> Thanks,
> Sumit
> >
> > --
> > Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2015-10-28 14:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15  8:09 [PATCH 02/12] megaraid_sas : Code optimization- remove PCI Ids based checks sumit.saxena
2015-10-16 14:39 ` Tomas Henzl
2015-10-19  5:48   ` Sumit Saxena
2015-10-19 11:59     ` Tomas Henzl
2015-10-28  2:33 ` Martin K. Petersen
2015-10-28  7:43   ` Sumit Saxena
2015-10-28 14:30     ` Kashyap Desai [this message]
2015-10-29  4:40       ` 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=c184826206ec6525b7ecb9e034cb6368@mail.gmail.com \
    --to=kashyap.desai@avagotech.com \
    --cc=hch@infradead.org \
    --cc=jbottomley@parallels.com \
    --cc=kiran-kumar.kasturi@avagotech.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).