From: Suraj Upadhyay <usuraj35@gmail.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: kashyap.desai@broadcom.com, sumit.saxena@broadcom.com,
shivasharan.srikanteshwara@broadcom.com, jejb@linux.ibm.com,
megaraidlinux.pdl@broadcom.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 1/2] scsi: megaraid: Remove pci-dma-compat wrapper APIs.
Date: Wed, 29 Jul 2020 23:50:42 +0530 [thread overview]
Message-ID: <20200729182042.GA17008@blackclown> (raw)
In-Reply-To: <yq1h7tr80ij.fsf@ca-mkp.ca.oracle.com>
On Tue, Jul 28, 2020 at 11:40:12PM -0400, Martin K. Petersen wrote:
>
> Hello Suraj!
>
> > The legacy API wrappers in include/linux/pci-dma-compat.h
> > should go away as it creates unnecessary midlayering
> > for include/linux/dma-mapping.h APIs, instead use dma-mapping.h
> > APIs directly.
>
> Instead of all these individual patches, please submit a combined patch
> series for the changes under SCSI.
>
> Each patch should fix a single driver. Please don't mix changes to
> completely different drivers such as hpsa and dc395x in a single
> commit. And please don't split semantically identical changes to the
> same driver into multiple commits (megaraid [2/2]).
>
> Thank you!
>
Hii Martin,
Thanks for your response.
I sent a patch series for the above changes.
Thanks,
Suraj Upadhyay
> --
> Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2020-07-29 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 14:08 [PATCH RESEND 1/2] scsi: megaraid: Remove pci-dma-compat wrapper APIs Suraj Upadhyay
2020-07-29 3:40 ` Martin K. Petersen
2020-07-29 18:20 ` Suraj Upadhyay [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=20200729182042.GA17008@blackclown \
--to=usuraj35@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=megaraidlinux.pdl@broadcom.com \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=sumit.saxena@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox