From: Lee Jones <lee.jones@linaro.org>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] mfd: Add ENE KB3930 Embedded Controller driver
Date: Mon, 27 Apr 2020 07:48:24 +0100 [thread overview]
Message-ID: <20200427064824.GB3559@dell> (raw)
In-Reply-To: <20200424221123.106527-1-lkundrak@v3.sk>
On Sat, 25 Apr 2020, Lubomir Rintel wrote:
> Hi,
>
> please take a look at the following patch set and consider applying it
> to the MFD tree. It a new driver with DT binding documentation changes,
> utilized by the LED driver submitted here:
>
> https://lore.kernel.org/lkml/20200424220240.106055-1-lkundrak@v3.sk/
What is this? The subject suggests this is a cover-letter for a
patch-set, but the patches are not attached to it. If this is the
case, please ensure that you send it --threaded using
`git send-email`
If it's just a random plea to go look at some set posted onto a
mailing list without me on Cc, then no. Please send the set again,
properly, with me listed as a recipient.
> Compared to v1 the dt-bindings validation failure has been fixed.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2020-04-27 6:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 22:11 [PATCH v2 0/2] mfd: Add ENE KB3930 Embedded Controller driver Lubomir Rintel
2020-04-24 22:11 ` [PATCH v2 1/2] dt-bindings: mfd: Add ENE KB3930 Embedded Controller binding Lubomir Rintel
2020-05-11 22:23 ` Rob Herring
2020-04-24 22:11 ` [PATCH v2 2/2] mfd: ene-kb3930: Add driver for ENE KB3930 Embedded Controller Lubomir Rintel
2020-04-29 6:00 ` Lee Jones
2020-05-04 19:23 ` Lubomir Rintel
2020-05-19 10:49 ` Lee Jones
2020-04-27 6:48 ` Lee Jones [this message]
2020-04-27 14:55 ` [PATCH v2 0/2] mfd: Add ENE KB3930 Embedded Controller driver Lubomir Rintel
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=20200427064824.GB3559@dell \
--to=lee.jones@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=mark.rutland@arm.com \
--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.