public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Biju Das <biju.das.jz@bp.renesas.com>,
	"nobuhiro1.iwamatsu@toshiba.co.jp"
	<nobuhiro1.iwamatsu@toshiba.co.jp>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] [PATCH 6.12.y-cip 0/8] RZ/G2L DU enhancements
Date: Mon, 14 Jul 2025 10:34:25 +0200	[thread overview]
Message-ID: <aHTBEeihrQH1PJBq@duo.ucw.cz> (raw)
In-Reply-To: <185211008098CFED.7957@lists.cip-project.org>

[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]

Hi!

> > > > This patch series for enhancing RZ/G2L DU driver.
> > > > All the patches are cherry-picked from mainline.
> > > 
> > > Thank you, looks good to me. I assume it is same as 6.1 version?
> > > 
> > > Mailing list damaged the patches, but 6.1 version came in ok, so I guess I can just apply that
> > > instead. (Assuming no other comments and okay tests).
> > > 
> > > (And I guess we should think about sending patches as one series "6.1,
> > > 6.12 -- subject", when they are identical).
> > 
> > Yes, I agree. But I have notices that, sometimes cherry-pick adjusts the line position for patches
> > automatically even though it is identical patches across 5.10/6.1/6.12.
> > In such cases, if applying patch fails one can cherry-pick it.
> 
> Aha, yes, so that can no longer be automatically applied.
> 
> Can I ask for re-send of the patch to pavel@denx.de? Unfortunately
> mailing list damaged this set and I don't see a way to easily pull
> them out of mailing list archives.

Standby. I believe I got good copy from patchwork.

Best regards,
								Pavel
-- 
In cooperation with DENX Software Engineering GmbH, HRB 165235 Munich,
Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2025-07-14  8:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 15:56 [PATCH 6.12.y-cip 0/8] RZ/G2L DU enhancements Biju Das
2025-07-11 15:56 ` [PATCH 6.12.y-cip 1/8] drm: renesas: rz-du: Drop DU_MCR0_DPI_OE macro Biju Das
2025-07-11 15:56 ` [PATCH 6.12.y-cip 2/8] drm: renesas: rz-du: rzg2l_du_encoder: Fix max dot clock for DPI Biju Das
2025-07-11 15:56 ` [PATCH 6.12.y-cip 3/8] drm: renesas: rz-du: Add Kconfig dependency between RZG2L_DU and RZG2L_MIPI_DSI Biju Das
2025-07-11 15:56 ` [PATCH 6.12.y-cip 4/8] drm: renesas: rz-du: Support dmabuf import Biju Das
2025-07-11 15:56 ` [PATCH 6.12.y-cip 5/8] drm: renesas: rz-du: Drop bpp variable from struct rzg2l_du_format_info Biju Das
2025-07-11 15:56 ` [PATCH 6.12.y-cip 6/8] drm: renesas: Extend RZ/G2L supported KMS formats Biju Das
2025-07-11 15:56 ` [PATCH 6.12.y-cip 7/8] drm: renesas: Add zpos, alpha and blend properties to RZ/G2L DU Biju Das
2025-07-11 15:56 ` [PATCH 6.12.y-cip 8/8] drm: renesas: rz-du: rzg2l_mipi_dsi: Update the comment in rzg2l_mipi_dsi_start_video() Biju Das
2025-07-13  9:58 ` [cip-dev] [PATCH 6.12.y-cip 0/8] RZ/G2L DU enhancements Pavel Machek
2025-07-13 18:57   ` Biju Das
2025-07-14  8:31     ` Pavel Machek
     [not found]     ` <185211008098CFED.7957@lists.cip-project.org>
2025-07-14  8:34       ` Pavel Machek [this message]
2025-07-14  9:37 ` Pavel Machek
2025-07-15  1:16 ` nobuhiro1.iwamatsu

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=aHTBEeihrQH1PJBq@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.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