public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: nobuhiro.iwamatsu.x90@mail.toshiba, pavel@nabladev.com
Cc: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] [PATCH 6.1.y-cip 00/17] Add RZ/G3S PCIe support
Date: Wed, 1 Apr 2026 07:14:28 +0300	[thread overview]
Message-ID: <fc9fce75-6f6c-4753-8bc7-c14bd03d2731@tuxon.dev> (raw)
In-Reply-To: <TY7PR01MB14818E4EF12163C4F09CDE5AECD48A@TY7PR01MB14818.jpnprd01.prod.outlook.com>

Hi, CIP maintainers,


On 3/24/26 11:10, Nobuhiro Iwamatsu via lists.cip-project.org wrote:
> Hi Claudiu,
> 
>> -----Original Message-----
>> From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
>> Sent: Monday, March 23, 2026 8:06 PM
>> To: iwamatsu nobuhiro(岩松 信洋 □DITC○CPT) <nobuhiro.iwamatsu.x90@mail.toshiba>; pavel@nabladev.com
>> Cc: cip-dev@lists.cip-project.org
>> Subject: Re: [cip-dev] [PATCH 6.1.y-cip 00/17] Add RZ/G3S PCIe support
>>
>> Hi, CIP maintainers,
>>
>> Gentle ping on this series and the v6.1, v6.12 backports.
> 
> Sorry for the delay in my review.
> I checked each version, and everything seems to be fine.
> If tests are OK and there is no comment, I can apply.
> 
> Reviewed-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.x90@mail.toshiba>
> 
Would you please let me know if there's anything I should be doing for this 
series (and the v5.10, v6.12 variants) to get merged?

Thank you,
Claudiu


  reply	other threads:[~2026-04-01  4:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <189BC4ACC53FCB81.1328210@lists.cip-project.org>
2026-03-23 11:05 ` [cip-dev] [PATCH 6.1.y-cip 00/17] Add RZ/G3S PCIe support Claudiu Beznea
2026-03-24  9:10   ` nobuhiro.iwamatsu.x90
2026-04-01  4:14     ` Claudiu Beznea [this message]
2026-04-01  5:33       ` nobuhiro.iwamatsu.x90
2026-04-01  5:22     ` nobuhiro.iwamatsu.x90

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=fc9fce75-6f6c-4753-8bc7-c14bd03d2731@tuxon.dev \
    --to=claudiu.beznea@tuxon.dev \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro.iwamatsu.x90@mail.toshiba \
    --cc=pavel@nabladev.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