Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Mark Brown <broonie@kernel.org>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	"biju.das.au" <biju.das.au@gmail.com>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v5 2/7] memory: renesas-rpc-if: Move rpc-if reg definitions
Date: Thu, 1 May 2025 12:16:40 +0200	[thread overview]
Message-ID: <5aab3f6f-cc58-4768-90a8-1dbee9ea1aeb@kernel.org> (raw)
In-Reply-To: <TY3PR01MB113463F1877B0335DD574AF5986822@TY3PR01MB11346.jpnprd01.prod.outlook.com>

On 01/05/2025 07:42, Biju Das wrote:
> Hi Krzysztof Kozlowski,
> 
>> -----Original Message-----
>> From: Krzysztof Kozlowski <krzk@kernel.org>
>> Subject: Re: [PATCH v5 2/7] memory: renesas-rpc-if: Move rpc-if reg definitions
>>
>> On 24/04/2025 10:59, Biju Das wrote:
>>> Move rpc-if reg definitions to a header file for the preparation of
>>> adding support for RZ/G3E XSPI that has different register definitions.
>>>
>>> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>>> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
>>> ---
>>> v4->v5:
>>>  * No change.
>>> v3->v4:
>>>  * Collected tag.
>>
>> Why are you sending patches which were two weeks before?
>>
>> This does not apply now, rebase.
> 
> It won't apply against mem-ctrl-next as you haven't added [1] and [2] from for-v6.16/renesas-rpc-if.

That's a topic branch and generic branch, what are talking about?

But anyway, if you claim it won't apply there and it does not apply on
my topic branch, where can I apply it? How do you imagine this works?

> I see patches [1] and [2] in next and for-v6.16/renesas-rpc-if [3].

So they were applied, therefore why are you sending them again?

> 
> Please let me know if I have missed anything.
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20250430&id=bf657e234ac12923b579b13d8b9f1b5ca0519697
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20250430&id=74c35c84f2ba942e7a7744658a8257d0b3188ac2
> [3] https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git/log/?h=for-v6.16/renesas-rpc-if
> 
> Cheers,
> Biju
> 


Best regards,
Krzysztof

  reply	other threads:[~2025-05-01 10:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24  8:59 [PATCH v5 0/7] Add RZ/G3E xSPI support Biju Das
2025-04-24  8:59 ` [PATCH v5 1/7] dt-bindings: memory: Document RZ/G3E support Biju Das
2025-05-01 10:25   ` (subset) " Krzysztof Kozlowski
2025-04-24  8:59 ` [PATCH v5 2/7] memory: renesas-rpc-if: Move rpc-if reg definitions Biju Das
2025-04-30 18:46   ` Krzysztof Kozlowski
2025-05-01  5:42     ` Biju Das
2025-05-01 10:16       ` Krzysztof Kozlowski [this message]
2025-05-01 10:25   ` (subset) " Krzysztof Kozlowski
2025-04-24  8:59 ` [PATCH v5 3/7] memory: renesas-rpc-if: Use devm_reset_control_array_get_exclusive() Biju Das
2025-04-30 18:46   ` Krzysztof Kozlowski
2025-05-01  5:56     ` Biju Das
2025-05-01 10:21       ` Krzysztof Kozlowski
2025-05-01 10:25   ` (subset) " Krzysztof Kozlowski
2025-04-24  8:59 ` [PATCH v5 4/7] memory: renesas-rpc-if: Add regmap to struct rpcif_info Biju Das
2025-05-01 10:25   ` (subset) " Krzysztof Kozlowski
2025-04-24  8:59 ` [PATCH v5 5/7] memory: renesas-rpc-if: Add wrapper functions Biju Das
2025-05-01 10:25   ` (subset) " Krzysztof Kozlowski
2025-04-24  8:59 ` [PATCH v5 6/7] memory: renesas-rpc-if: Add RZ/G3E xSPI support Biju Das
2025-05-01 10:25   ` (subset) " Krzysztof Kozlowski
2025-04-24  8:59 ` [PATCH v5 7/7] spi: rpc-if: Add write support for memory-mapped area Biju Das
2025-05-08  9:08   ` Krzysztof Kozlowski
2025-05-01 10:23 ` [PATCH v5 0/7] Add RZ/G3E xSPI support Krzysztof Kozlowski
2025-05-10  1:51 ` (subset) " Mark Brown

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=5aab3f6f-cc58-4768-90a8-1dbee9ea1aeb@kernel.org \
    --to=krzk@kernel.org \
    --cc=biju.das.au@gmail.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=broonie@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-renesas-soc@vger.kernel.org \
    --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