From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Tomas Henzl <thenzl@redhat.com>,
Sathya Prakash <sathya.prakash@avagotech.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Alexey Khoroshilov <khoroshilov@ispras.ru>,
Sreekanth Reddy <sreekanth.reddy@avagotech.com>,
PDL-MPT-FUSIONLINUX <MPT-FusionLinux.pdl@avagotech.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
ldv-project@linuxtesting.org
Subject: Re: [PATCH v3] mptlan: add checks for dma mapping errors
Date: Wed, 27 Jan 2016 08:23:41 -0800 [thread overview]
Message-ID: <1453911821.2322.13.camel@HansenPartnership.com> (raw)
In-Reply-To: <56A8ECCD.2010102@redhat.com>
On Wed, 2016-01-27 at 17:14 +0100, Tomas Henzl wrote:
> On 27.1.2016 06:44, Sathya Prakash wrote:
> > There is no fusion based network card and resources exists today in
> > Avago(LSI) to test this patch so we prefer to leave it as is. We
> > would
> > like to prevent any new changes on MPT (FC/SCSI/SAS/LAN) drivers as
> > we
> > don't have support for those cards anymore, is there a way we
> > could
> > remove those drivers from newer kernels or mark them as
> > unmaintained?.
>
> There still are users of some of those drivers (mptsas for example)
> in certain distributions, so even if in fact they aren't
> directly maintained, we should keep them in mainline.
Agreed: the last gen PA-RISC has a mptspi controller ... they'd get a
bit annoyed if we remove it because they wouldn't be able to update
their build machines to newer kernels.
James
prev parent reply other threads:[~2016-01-27 16:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 0:41 [PATCH v2] mptlan: add checks for dma mapping errors Alexey Khoroshilov
2016-01-25 15:36 ` Tomas Henzl
2016-01-25 17:08 ` Alexey Khoroshilov
2016-01-25 17:08 ` Alexey Khoroshilov
2016-01-25 18:02 ` [PATCH v3] " Alexey Khoroshilov
2016-01-26 16:33 ` Tomas Henzl
2016-01-27 2:22 ` Martin K. Petersen
2016-01-27 5:44 ` Sathya Prakash
2016-01-27 16:14 ` Tomas Henzl
2016-01-27 16:23 ` James Bottomley [this message]
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=1453911821.2322.13.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=MPT-FusionLinux.pdl@avagotech.com \
--cc=khoroshilov@ispras.ru \
--cc=ldv-project@linuxtesting.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sathya.prakash@avagotech.com \
--cc=sreekanth.reddy@avagotech.com \
--cc=thenzl@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.