From: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
To: Melissa Wen <melissa.srw@gmail.com>
Cc: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>,
Leo Li <sunpeng.li@amd.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
David Airlie <airlied@linux.ie>,
amd-gfx@lists.freedesktop.org,
Alex Deucher <alexander.deucher@amd.com>,
Christian Konig <christian.koenig@amd.com>
Subject: Re: [PATCH 0/2] drm/amd/display: dc_link: cleaning up some code style issues
Date: Thu, 27 Feb 2020 10:05:18 -0500 [thread overview]
Message-ID: <20200227150518.tchch32d4lcjripr@outlook.office365.com> (raw)
In-Reply-To: <cover.1582752490.git.melissa.srw@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1361 bytes --]
Hi Melissa,
First of all, thank you very much for this patchset; in general,
everything looks good to me.
I noticed that your patchset does not apply because you made your
changes based on `drm-misc-next`; when you send patches to amdgpu, use
the following repository:
git://people.freedesktop.org/~agd5f/linux
Could you prepare a V2?
Thanks!
On 02/26, Melissa Wen wrote:
> This patchset solves some coding style issues on dc_link for readability
> and cleaning up warnings. Change suggested by checkpatch.pl.
>
> Melissa Wen (2):
> drm/amd/display: dc_link: code clean up on enable_link_dp function
> drm/amd/display: dc_link: code clean up on detect_dp function
>
> drivers/gpu/drm/amd/display/dc/core/dc_link.c | 67 +++++++++----------
> 1 file changed, 32 insertions(+), 35 deletions(-)
>
> --
> 2.25.0
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Fdri-devel&data=02%7C01%7CRodrigo.Siqueira%40amd.com%7C7a3e02e3f43447ed4fab08d7bb080d9b%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637183515885211986&sdata=bnipkrUtKdO1oOKxdt1th4iIG1%2BBgl2wMPVrdmn3P1U%3D&reserved=0
--
Rodrigo Siqueira
https://siqueira.tech
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-02-27 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 22:05 [PATCH 0/2] drm/amd/display: dc_link: cleaning up some code style issues Melissa Wen
2020-02-26 22:07 ` [PATCH 1/2] drm/amd/display: dc_link: code clean up on enable_link_dp function Melissa Wen
2020-02-27 15:04 ` Rodrigo Siqueira
2020-02-26 22:08 ` [PATCH 2/2] drm/amd/display: dc_link: code clean up on detect_dp function Melissa Wen
2020-02-27 18:39 ` Liu, Zhan
2020-02-27 18:48 ` Liu, Zhan
2020-02-27 15:05 ` Rodrigo Siqueira [this message]
2020-02-27 18:38 ` [PATCH 0/2] drm/amd/display: dc_link: cleaning up some code style issues Melissa Wen
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=20200227150518.tchch32d4lcjripr@outlook.office365.com \
--to=rodrigo.siqueira@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=melissa.srw@gmail.com \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=sunpeng.li@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).