All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: Corentin Labbe <clabbe@baylibre.com>,
	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 01:32:15 +0100	[thread overview]
Message-ID: <CACRpkdbJ2c0X4Oh8-Daw9O4Qk3ZWJQSkN171Ox7K9DnGbVhp3Q@mail.gmail.com> (raw)
In-Reply-To: <2b0fa854-16e7-3d0b-a04a-971249646fab@opensource.wdc.com>

On Mon, Jan 31, 2022 at 12:56 AM Damien Le Moal
<damien.lemoal@opensource.wdc.com> wrote:
> 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 !

I am referring to the situation before
commit 5ac749a57e0ebb334b1b2c3d28d4d5b1ef85f8ed
I am happy that this is now solved!

Sorry for not being up-to-date.

Yours,
Linus Walleij

  reply	other threads:[~2022-01-31  0:32 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
2022-01-31  0:32     ` Linus Walleij [this message]
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=CACRpkdbJ2c0X4Oh8-Daw9O4Qk3ZWJQSkN171Ox7K9DnGbVhp3Q@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=clabbe@baylibre.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=devicetree@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.