From: Daniel Vetter <daniel@ffwll.ch>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: David Airlie <airlied@linux.ie>,
arcml <linux-snps-arc@lists.infradead.org>,
Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [GIT PULL] drm/arc: Yet another set of minor fixes
Date: Fri, 13 Dec 2019 11:22:19 +0100 [thread overview]
Message-ID: <20191213102219.GE624164@phenom.ffwll.local> (raw)
In-Reply-To: <CY4PR1201MB0120529194B092E2C2ACD77EA1540@CY4PR1201MB0120.namprd12.prod.outlook.com>
On Fri, Dec 13, 2019 at 10:20:39AM +0000, Alexey Brodkin wrote:
> Hi Daniel,
>
> [snip]
>
> > > Thanks for the pointers
> > >
> > > > Or respin this one, but these small pulls have a habit of occasionally
> > > > getting lost :-/
> > >
> > > Well I'd better re-spin this, see below.
> > >
> > > The following changes since commit acc61b8929365e63a3e8c8c8913177795aa45594:
> > >
> > > Merge tag 'drm-next-5.5-2019-11-22' of git://people.freedesktop.org/~agd5f/linux into drm-next
> > (2019-11-26 08:40:23 +1000)
> > >
> > > are available in the Git repository at:
> > >
> > > git@github.com:abrodkin/linux.git tags/arcpgu-updates-2019.11.27
> > >
> > > for you to fetch changes up to 9c2acc26c899aa12ad009dff10a5573ef769a7fd:
> > >
> > > DRM: ARC: PGU: add ARGB8888 format to supported format list (2019-11-27 16:43:39 +0300)
> > >
> > > ----------------------------------------------------------------
> > > Clean-up and fixes for FourCC handling in ARC PGU.
> > >
> > > ----------------------------------------------------------------
> > > Eugeniy Paltsev (4):
> > > DRM: ARC: PGU: fix framebuffer format switching
> > > DRM: ARC: PGU: cleanup supported format list code
> > > DRM: ARC: PGU: replace unsupported by HW RGB888 format by XRGB888
> > > DRM: ARC: PGU: add ARGB8888 format to supported format list
> > >
> > > drivers/gpu/drm/arc/arcpgu_crtc.c | 36 ++++++++++++++++++------------------
> > > drivers/gpu/drm/arc/arcpgu_regs.h | 2 +-
> > > 2 files changed, 19 insertions(+), 19 deletions(-)
>
> Not sure if you noticed re-spin of my pull-request in the previous message.
> Do you want me to send it in a separate email?
Yeah I guess this got lost again.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next prev parent reply other threads:[~2019-12-13 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 7:48 [GIT PULL] drm/arc: Yet another set of minor fixes Alexey Brodkin
2019-11-27 10:06 ` Daniel Vetter
2019-11-27 13:49 ` Alexey Brodkin
2019-11-27 14:06 ` Daniel Vetter
2019-12-13 10:20 ` Alexey Brodkin
2019-12-13 10:22 ` Daniel Vetter [this message]
2019-12-13 10:24 ` Alexey Brodkin
2019-12-16 10:28 ` Daniel Vetter
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=20191213102219.GE624164@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-snps-arc@lists.infradead.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).