From: Basavaraj Natikar <bnatikar@amd.com>
To: Jiri Kosina <jikos@kernel.org>,
Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Cc: Nehal Shah <nehal-bakulchandra.shah@amd.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
"open list:AMD SENSOR FUSION HUB DRIVER"
<linux-input@vger.kernel.org>
Subject: Re: [PATCH 0/4] Fixes and updates to amd-sfh driver
Date: Mon, 27 Sep 2021 13:26:27 +0530 [thread overview]
Message-ID: <1bb8c251-2506-d8c4-c93c-4e281803943f@amd.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2109270945170.15944@cbobk.fhfr.pm>
On 9/27/2021 1:16 PM, Jiri Kosina wrote:
> [CAUTION: External Email]
>
> On Thu, 23 Sep 2021, Basavaraj Natikar wrote:
>
>> Changes include fix to NULL pointer dereference, remove pci_ wrappers,
>> use dma_set_mask_and_coherent and copyright updates.
>>
>> Basavaraj Natikar (4):
>> amd_sfh: Fix potential NULL pointer dereference
>> amd_sfh: Use dma_set_mask_and_coherent()
> Thanks for the patches. My plan is to push the two above as 5.15 material
> (fixes), and queue the 2 below as 5.16 merge window material. Please
> holler if you disagree.
>
>> amd_sfh: switch from 'pci_' to 'dev_' API
>> amd_sfh: Update Copyright details
Makes sense. Appreciate your help.
Thanks,
Basavaraj
prev parent reply other threads:[~2021-09-27 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 12:29 [PATCH 0/4] Fixes and updates to amd-sfh driver Basavaraj Natikar
2021-09-23 12:29 ` [PATCH 1/4] amd_sfh: Fix potential NULL pointer dereference Basavaraj Natikar
2021-09-23 12:29 ` [PATCH 2/4] amd_sfh: Use dma_set_mask_and_coherent() Basavaraj Natikar
2021-09-23 12:29 ` [PATCH 3/4] amd_sfh: switch from 'pci_' to 'dev_' API Basavaraj Natikar
2021-09-23 12:29 ` [PATCH 4/4] amd_sfh: Update Copyright details Basavaraj Natikar
2021-09-27 7:46 ` [PATCH 0/4] Fixes and updates to amd-sfh driver Jiri Kosina
2021-09-27 7:56 ` Basavaraj Natikar [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=1bb8c251-2506-d8c4-c93c-4e281803943f@amd.com \
--to=bnatikar@amd.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=nehal-bakulchandra.shah@amd.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).