From: Markus Elfring <Markus.Elfring@web.de>
To: Alex Dewar <alex.dewar@gmx.co.uk>, linux-scsi@vger.kernel.org
Cc: Allison Randal <allison@lohutok.net>,
Arnd Bergmann <arnd@arndb.de>,
Julia Lawall <julia.lawall@inria.fr>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Himanshu Madhani <hmadhani@marvell.com>,
"James E. J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Richard Fontana <rfontana@redhat.com>,
Sathya Prakash <sathya.prakash@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
Thomas Gleixner <tglx@linutronix.de>,
aacraid@microsemi.com, MPT-FusionLinux.pdl@broadcom.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: Remove unnecessary calls to memset after dma_alloc_coherent
Date: Thu, 9 Apr 2020 16:06:44 +0200 [thread overview]
Message-ID: <099aaf53-739c-568d-df7c-e9a2d56a07fd@web.de> (raw)
In-Reply-To: <20200409114218.5muicchv37ulrjxf@medion>
>> * Would you like to extend your skills in corresponding areas anyhow?
>
> Sure, I'd love to. Are there any resources you'd recommend?
How helpful do you find the available software documentation
(and other communication interfaces)?
Regards,
Markus
next prev parent reply other threads:[~2020-04-09 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 11:14 [PATCH] scsi: Remove unnecessary calls to memset after dma_alloc_coherent Markus Elfring
2020-04-07 16:02 ` Alex Dewar
2020-04-07 16:56 ` Markus Elfring
2020-04-09 11:42 ` Alex Dewar
2020-04-09 14:06 ` Markus Elfring [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-03 17:58 Alex Dewar
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=099aaf53-739c-568d-df7c-e9a2d56a07fd@web.de \
--to=markus.elfring@web.de \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=aacraid@microsemi.com \
--cc=alex.dewar@gmx.co.uk \
--cc=allison@lohutok.net \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=hmadhani@marvell.com \
--cc=jejb@linux.ibm.com \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=rfontana@redhat.com \
--cc=sathya.prakash@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.com \
--cc=tglx@linutronix.de \
/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