From: "Agrawal, Akshu" <Akshu.Agrawal@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>,
"Mukunda,Vijendar" <vijendar.mukunda@amd.com>
Cc: Daniel Kurtz <djkurtz@chromium.org>,
"Deucher, Alexander" <alexander.deucher@amd.com>,
David Airlie <airlied@linux.ie>,
LKML <linux-kernel@vger.kernel.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
jclinton@chromium.org,
dri-devel <dri-devel@lists.freedesktop.org>,
Christian Koenig <christian.koenig@amd.com>
Subject: Re: [PATCH] drm/amdgpu/acp: Fix slab-out-of-bounds in mfd_add_device in acp_hw_init
Date: Mon, 9 Jul 2018 12:10:30 +0530 [thread overview]
Message-ID: <ae639d60-9fc9-04fe-debd-ac1c3be86d16@amd.com> (raw)
In-Reply-To: <CADnq5_Me=_g6St_j8fYy20eiZK6fbmdp3zZ9WQMM5S5BuZY6uQ@mail.gmail.com>
>>>> Was this patch ever picked up? I can't find it in agd5f/linux.
>>>
>>>
>>> It wasn't applied. I don't see 51f7415039d4 ("drm/amd/amdgpu:
>>> creating two I2S instances for stoney/cz") upstream yet either.
>>> Daniel, Vijendar, which ones do you want applied? Can you send me the
>>> patches?
>>>
>>> Alex
>>
>>
>> Hi Alex,
>>
>> "drm/amd/amdgpu: creating two I2S instances for stoney/cz" patch exists in
>> drm-next branch. Please pick the patch .
>
> So just that one? I seem to recall there being later revisions of
> that patch that you reworked after applying the original version.
> Also that patch was originally part of a larger series. Are those
> changes required too?
>
> Alex
>
Hi Alex,
In agd5f/linux, branch "amd-staging-drm-next",
506f7d1 drm/amd/amdgpu: creating two I2S instances for stoney/cz
patch is present.
This patch is the correct version and there aren't any other changes
required with it.
Only Dan's, this mail's patch is currently missing form the tree.
Thanks,
Akshu
prev parent reply other threads:[~2018-07-09 6:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 16:15 [PATCH] drm/amdgpu/acp: Fix slab-out-of-bounds in mfd_add_device in acp_hw_init Daniel Kurtz
2018-04-16 3:47 ` Agrawal, Akshu
2018-07-02 21:48 ` Daniel Kurtz
2018-07-03 16:20 ` Alex Deucher
2018-07-04 8:48 ` Mukunda,Vijendar
2018-07-05 16:38 ` Alex Deucher
2018-07-09 6:40 ` Agrawal, Akshu [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=ae639d60-9fc9-04fe-debd-ac1c3be86d16@amd.com \
--to=akshu.agrawal@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=djkurtz@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jclinton@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vijendar.mukunda@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).