From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Corentin Labbe <clabbe@baylibre.com>
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: ata: convert ata/cortina,gemini-sata-bridge to yaml
Date: Mon, 31 Jan 2022 08:56:41 +0900 [thread overview]
Message-ID: <2b0fa854-16e7-3d0b-a04a-971249646fab@opensource.wdc.com> (raw)
In-Reply-To: <CACRpkdb9R-BwdVzyeaQOjagsQU=2-06VNqKPG9fMa7C93eDC7A@mail.gmail.com>
On 2022/01/30 9:26, Linus Walleij wrote:
> Thanks for doing this Corentin!
>
> On Sat, Jan 29, 2022 at 9:40 PM Corentin Labbe <clabbe@baylibre.com> wrote:
>
>> This patch converts ata/cortina,gemini-sata-bridge binding to yaml
>>
>> Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> Knowing that drivers/ata is a bit sparsely maintained I suggest that Rob apply
> this patch when he feels it looks good.
What do you mean ? I am doing my best here to maintain ata !
But I definitely do not have all the hardware supported for testing :)
That said, I am perfectly fine with Rob taking device tree patches if that is
not a problem for him.
>
> Yours,
> Linus Walleij
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-01-30 23:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 20:40 [PATCH] dt-bindings: ata: convert ata/cortina,gemini-sata-bridge to yaml Corentin Labbe
2022-01-30 0:26 ` Linus Walleij
2022-01-30 23:56 ` Damien Le Moal [this message]
2022-01-31 0:32 ` Linus Walleij
2022-02-01 17:36 ` Sergei Shtylyov
2022-02-01 22:56 ` Damien Le Moal
2022-02-02 9:24 ` Sergei Shtylyov
2022-02-02 10:46 ` Damien Le Moal
2022-01-31 0:48 ` Damien Le Moal
2022-01-31 8:11 ` LABBE Corentin
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=2b0fa854-16e7-3d0b-a04a-971249646fab@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=clabbe@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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).