From: Sean Paul <seanpaul@chromium.org>
To: Mark Yao <mark.yao@rock-chips.com>
Cc: David Airlie <airlied@linux.ie>, Heiko Stuebner <heiko@sntech.de>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] drm/rockchip: Some fixes
Date: Wed, 9 Aug 2017 09:38:34 -0400 [thread overview]
Message-ID: <CAOw6vbJr5Ya5Lyd3MqhSZd=mPaKzCwcBeSGfJLtv=kFUDvXbhw@mail.gmail.com> (raw)
In-Reply-To: <1501494569-6825-1-git-send-email-mark.yao@rock-chips.com>
On Mon, Jul 31, 2017 at 5:49 AM, Mark Yao <mark.yao@rock-chips.com> wrote:
> Here are some fixes port from rockchip_linux project[0],
>
> Tested on rk3399 and rk3288 board.
>
> [0]: https://github.com/rockchip-linux/kernel
>
> Mark Yao (6):
> drm/rockchip: vop: no need wait vblank on crtc enable
> drm/rockchip: vop: fix iommu page fault when resume
> drm/rockchip: vop: fix NV12 video display error
> drm/rockchip: vop: round_up pitches to word align
> drm/rockchip: vop: report error when check resource error
> drm/rockchip: fix race with kms hotplug and fbdev
Hi Mark,
I noticed you applied this set to both -misc-next and -misc-fixes. In
the future, please do not apply patches in both places.
Instead, consult the flowchart under "Where Do I Apply My Patch?" at
https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-misc.html
and choose the most appropriate place. If you are unsure, please reach
out to a -misc maintainer.
Thank you,
Sean
>
> drivers/gpu/drm/rockchip/rockchip_drm_fb.c | 2 +-
> drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 77 ++++++++---------------------
> drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 3 ++
> 3 files changed, 24 insertions(+), 58 deletions(-)
>
> --
> 1.9.1
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Sean Paul <seanpaul@chromium.org>
To: Mark Yao <mark.yao@rock-chips.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/6] drm/rockchip: Some fixes
Date: Wed, 9 Aug 2017 09:38:34 -0400 [thread overview]
Message-ID: <CAOw6vbJr5Ya5Lyd3MqhSZd=mPaKzCwcBeSGfJLtv=kFUDvXbhw@mail.gmail.com> (raw)
In-Reply-To: <1501494569-6825-1-git-send-email-mark.yao@rock-chips.com>
On Mon, Jul 31, 2017 at 5:49 AM, Mark Yao <mark.yao@rock-chips.com> wrote:
> Here are some fixes port from rockchip_linux project[0],
>
> Tested on rk3399 and rk3288 board.
>
> [0]: https://github.com/rockchip-linux/kernel
>
> Mark Yao (6):
> drm/rockchip: vop: no need wait vblank on crtc enable
> drm/rockchip: vop: fix iommu page fault when resume
> drm/rockchip: vop: fix NV12 video display error
> drm/rockchip: vop: round_up pitches to word align
> drm/rockchip: vop: report error when check resource error
> drm/rockchip: fix race with kms hotplug and fbdev
Hi Mark,
I noticed you applied this set to both -misc-next and -misc-fixes. In
the future, please do not apply patches in both places.
Instead, consult the flowchart under "Where Do I Apply My Patch?" at
https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-misc.html
and choose the most appropriate place. If you are unsure, please reach
out to a -misc maintainer.
Thank you,
Sean
>
> drivers/gpu/drm/rockchip/rockchip_drm_fb.c | 2 +-
> drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 77 ++++++++---------------------
> drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 3 ++
> 3 files changed, 24 insertions(+), 58 deletions(-)
>
> --
> 1.9.1
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: seanpaul@chromium.org (Sean Paul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] drm/rockchip: Some fixes
Date: Wed, 9 Aug 2017 09:38:34 -0400 [thread overview]
Message-ID: <CAOw6vbJr5Ya5Lyd3MqhSZd=mPaKzCwcBeSGfJLtv=kFUDvXbhw@mail.gmail.com> (raw)
In-Reply-To: <1501494569-6825-1-git-send-email-mark.yao@rock-chips.com>
On Mon, Jul 31, 2017 at 5:49 AM, Mark Yao <mark.yao@rock-chips.com> wrote:
> Here are some fixes port from rockchip_linux project[0],
>
> Tested on rk3399 and rk3288 board.
>
> [0]: https://github.com/rockchip-linux/kernel
>
> Mark Yao (6):
> drm/rockchip: vop: no need wait vblank on crtc enable
> drm/rockchip: vop: fix iommu page fault when resume
> drm/rockchip: vop: fix NV12 video display error
> drm/rockchip: vop: round_up pitches to word align
> drm/rockchip: vop: report error when check resource error
> drm/rockchip: fix race with kms hotplug and fbdev
Hi Mark,
I noticed you applied this set to both -misc-next and -misc-fixes. In
the future, please do not apply patches in both places.
Instead, consult the flowchart under "Where Do I Apply My Patch?" at
https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-misc.html
and choose the most appropriate place. If you are unsure, please reach
out to a -misc maintainer.
Thank you,
Sean
>
> drivers/gpu/drm/rockchip/rockchip_drm_fb.c | 2 +-
> drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 77 ++++++++---------------------
> drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 3 ++
> 3 files changed, 24 insertions(+), 58 deletions(-)
>
> --
> 1.9.1
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-08-09 13:38 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 9:49 [PATCH 0/6] drm/rockchip: Some fixes Mark Yao
2017-07-31 9:49 ` Mark Yao
2017-07-31 9:49 ` Mark Yao
2017-07-31 9:49 ` [PATCH 1/6] drm/rockchip: vop: no need wait vblank on crtc enable Mark Yao
2017-07-31 9:49 ` Mark Yao
2017-07-31 9:49 ` Mark Yao
2017-08-03 12:36 ` Sandy Huang
2017-08-03 12:36 ` Sandy Huang
2017-07-31 9:49 ` [PATCH 2/6] drm/rockchip: vop: fix iommu page fault when resume Mark Yao
2017-07-31 9:49 ` Mark Yao
2017-07-31 9:49 ` Mark Yao
2017-08-03 13:06 ` Sandy Huang
2017-08-03 13:06 ` Sandy Huang
2017-08-03 13:06 ` Sandy Huang
2017-07-31 9:49 ` [PATCH 3/6] drm/rockchip: vop: fix NV12 video display error Mark Yao
2017-07-31 9:49 ` Mark Yao
2017-08-04 0:56 ` Sandy Huang
2017-08-04 0:56 ` Sandy Huang
2017-08-04 0:56 ` Sandy Huang
2017-07-31 9:49 ` [PATCH 4/6] drm/rockchip: vop: round_up pitches to word align Mark Yao
2017-07-31 9:49 ` Mark Yao
2017-08-04 0:56 ` Sandy Huang
2017-08-04 0:56 ` Sandy Huang
2017-08-04 0:56 ` Sandy Huang
2017-07-31 9:49 ` [PATCH 5/6] drm/rockchip: vop: report error when check resource error Mark Yao
2017-07-31 9:49 ` Mark Yao
2017-07-31 9:49 ` Mark Yao
2017-08-04 0:57 ` Sandy Huang
2017-08-04 0:57 ` Sandy Huang
2017-08-04 0:57 ` Sandy Huang
2017-07-31 9:50 ` [PATCH 6/6] drm/rockchip: fix race with kms hotplug and fbdev Mark Yao
2017-07-31 9:50 ` Mark Yao
2017-07-31 11:57 ` Emil Velikov
2017-07-31 11:57 ` Emil Velikov
2017-07-31 12:28 ` Daniel Vetter
2017-07-31 12:28 ` Daniel Vetter
2017-07-31 12:28 ` Daniel Vetter
2017-08-01 2:00 ` Mark yao
2017-08-01 2:00 ` Mark yao
2017-08-01 8:11 ` [PATCH v1.1] " Mark Yao
2017-08-01 8:11 ` Mark Yao
2017-08-01 8:11 ` Mark Yao
2017-08-04 3:20 ` Sandy Huang
2017-08-04 3:20 ` Sandy Huang
2017-08-04 3:20 ` Sandy Huang
2017-08-09 13:38 ` Sean Paul [this message]
2017-08-09 13:38 ` [PATCH 0/6] drm/rockchip: Some fixes Sean Paul
2017-08-09 13:38 ` Sean Paul
-- strict thread matches above, loose matches on Subject: below --
2016-07-14 3:31 [PATCH 0/6] drm/rockchip: some fixes Mark Yao
2016-07-14 3:31 ` Mark Yao
2016-07-14 3:31 ` Mark Yao
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='CAOw6vbJr5Ya5Lyd3MqhSZd=mPaKzCwcBeSGfJLtv=kFUDvXbhw@mail.gmail.com' \
--to=seanpaul@chromium.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.yao@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.