From: Oleksandr Andrushchenko <Oleksandr_Andrushchenko@epam.com>
To: Daniel Vetter <daniel@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Cc: Wan Jiabing <wanjiabing@vivo.com>,
David Airlie <airlied@linux.ie>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kael_w@yeah.net" <kael_w@yeah.net>
Subject: Re: [PATCH] drivers: gpu: drm: xen_drm_front_drm_info is declared twice
Date: Thu, 25 Mar 2021 09:28:29 +0000 [thread overview]
Message-ID: <4f1747c4-6578-4962-f51d-6d3827d0034d@epam.com> (raw)
In-Reply-To: <CAKMK7uEpNexmDYar36ZEX0hbHoxH3Y+_D42NqjRwAqxpiCXHRA@mail.gmail.com>
Hi, Daniel!
On 3/25/21 11:16 AM, Daniel Vetter wrote:
> On Thu, Mar 25, 2021 at 7:53 AM Oleksandr Andrushchenko
> <Oleksandr_Andrushchenko@epam.com> wrote:
>> Hi,
>>
>> On 3/25/21 8:19 AM, Wan Jiabing wrote:
>>> struct xen_drm_front_drm_info has been declared.
>>> Remove the duplicate.
>>>
>>> Signed-off-by: Wan Jiabing <wanjiabing@vivo.com>
>> Thank you for the patch,
>>
>> Reviewed-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>>
>> Will apply to drm-misc-next-fixes
> drm-misc-next-fixes is the wrong tree, bugfixes outside of the merge
> window belong into drm-misc-fixes. Please consult
>
> https://urldefense.com/v3/__https://drm.pages.freedesktop.org/maintainer-tools/committer-drm-misc.html*where-do-i-apply-my-patch__;Iw!!GF_29dbcQIUBPA!nfKNXrB-yHqaxeH6nC3mEw28HFFI1p5fc5CZKEFeoQPWXEhZCpvMqvW8EtFfTqtHPiNgpY4S-g$ [drm[.]pages[.]freedesktop[.]org]
>
> We need to hard-reset drm-misc-next-fixes back, please re-apply the
> patches (both of them) to drm-misc-fixes. Also adding drm-misc
> maintainers.
Sorry for screwing things up, will re-apply both patches to drm-misc-fixes
> -Daniel
>
>> Thank you,
>>
>> Oleksandr
>>
>>> ---
>>> drivers/gpu/drm/xen/xen_drm_front_conn.h | 1 -
>>> 1 file changed, 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/xen/xen_drm_front_conn.h b/drivers/gpu/drm/xen/xen_drm_front_conn.h
>>> index 3adacba9a23b..e5f4314899ee 100644
>>> --- a/drivers/gpu/drm/xen/xen_drm_front_conn.h
>>> +++ b/drivers/gpu/drm/xen/xen_drm_front_conn.h
>>> @@ -16,7 +16,6 @@
>>> struct drm_connector;
>>> struct xen_drm_front_drm_info;
>>>
>>> -struct xen_drm_front_drm_info;
>>>
>>> int xen_drm_front_conn_init(struct xen_drm_front_drm_info *drm_info,
>>> struct drm_connector *connector);
>
>
prev parent reply other threads:[~2021-03-25 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 6:19 [PATCH] drivers: gpu: drm: xen_drm_front_drm_info is declared twice Wan Jiabing
2021-03-25 6:53 ` Oleksandr Andrushchenko
2021-03-25 9:16 ` Daniel Vetter
2021-03-25 9:18 ` Daniel Vetter
2021-03-25 9:28 ` Oleksandr Andrushchenko [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=4f1747c4-6578-4962-f51d-6d3827d0034d@epam.com \
--to=oleksandr_andrushchenko@epam.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kael_w@yeah.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
--cc=wanjiabing@vivo.com \
--cc=xen-devel@lists.xenproject.org \
/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).