From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bastien Curutchet <bastien.curutchet@bootlin.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>,
Christopher Cordahi <christophercordahi@nanometrics.ca>
Subject: Re: [PATCH 0/5] Implement setup_inteface() in the DaVinci NAND controller
Date: Wed, 30 Oct 2024 15:25:27 +0100 [thread overview]
Message-ID: <ae4b252d-ec74-4058-a1b4-4852e6de7eb6@kernel.org> (raw)
In-Reply-To: <fdf3d305-d6a9-47bb-b474-92da43b8d557@bootlin.com>
On 30/10/2024 13:39, Bastien Curutchet wrote:
> Hi Krzysztof,
>
> On 10/30/24 12:17 PM, Krzysztof Kozlowski wrote:
>> On 30/10/2024 11:47, Bastien Curutchet wrote:
>>> Hi all,
>>>
>>> This patch series aims to implement the setup_interface() operation in
>>> the DaVinci NAND controller to enable the use of all ONFI modes and
>>> improve the NAND access speed.
>>>
>>
>> Your changelog is supposed to explain also merging dependencies. Within
>> patchset or external.
>
> I'm not sure I understand what you mean here. Do you mean that I need to
> explicitly state that the patches in the
> drivers/mtd/nand/raw/davinci_nand.c depend on the ones in
> drivers/memory/ti-aemif.c ?
Well, you target different subsystems, so maintainers need to know what
they can take and what do you expect of them. Otherwise what do you
expect of me exactly and how can I guess it?
Best regards,
Krzysztof
prev parent reply other threads:[~2024-10-30 14:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 10:47 [PATCH 0/5] Implement setup_inteface() in the DaVinci NAND controller Bastien Curutchet
2024-10-30 10:47 ` [PATCH 1/5] memory: ti-aemif: Create aemif_set_cs_timings() Bastien Curutchet
2024-10-30 10:47 ` [PATCH 2/5] memory: ti-aemif: export aemif_set_cs_timing() Bastien Curutchet
2024-10-31 5:42 ` kernel test robot
2024-10-30 10:47 ` [PATCH 3/5] mtd: rawnand: davinci: Order headers alphabetically Bastien Curutchet
2024-10-30 10:47 ` [PATCH 4/5] mtd: rawnand: davinci: Add clock resource Bastien Curutchet
2024-10-30 11:17 ` Krzysztof Kozlowski
2024-10-30 12:20 ` Bastien Curutchet
2024-10-30 14:26 ` Krzysztof Kozlowski
2024-10-30 10:47 ` [PATCH 5/5] mtd: rawnand: davinci: Implement setup_interface() operation Bastien Curutchet
2024-11-01 18:11 ` kernel test robot
2024-11-02 2:04 ` kernel test robot
2024-10-30 11:17 ` [PATCH 0/5] Implement setup_inteface() in the DaVinci NAND controller Krzysztof Kozlowski
2024-10-30 12:39 ` Bastien Curutchet
2024-10-30 14:25 ` Krzysztof Kozlowski [this message]
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=ae4b252d-ec74-4058-a1b4-4852e6de7eb6@kernel.org \
--to=krzk@kernel.org \
--cc=bastien.curutchet@bootlin.com \
--cc=christophercordahi@nanometrics.ca \
--cc=herve.codina@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=ssantosh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vigneshr@ti.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