From: Marek Vasut <marex@denx.de>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH v2] dt-bindings: leds: Document mmc trigger
Date: Fri, 25 Feb 2022 00:08:17 +0100 [thread overview]
Message-ID: <1e4dc8c2-daa7-3cef-eaf5-76616b6230a3@denx.de> (raw)
In-Reply-To: <YhgHTrlxyn5QGdOM@robh.at.kernel.org>
On 2/24/22 23:31, Rob Herring wrote:
> On Thu, Feb 17, 2022 at 06:43:57PM +0100, Marek Vasut wrote:
>> The mmc subsystem supports triggering leds on card activity, document
>> the trigger value here. The value is a pattern in this case.
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>> Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>
>> Cc: Pavel Machek <pavel@ucw.cz>
>> Cc: Rob Herring <robh+dt@kernel.org>
>> Cc: devicetree@vger.kernel.org
>> To: linux-leds@vger.kernel.org
>> ---
>> V2: Rebase on next-20220217
>
> Why? Nobody can apply patches to linux-next. Is there something in next
> you are dependent on that you didn't tell us about?
It is just a convenience really, it is where the commits for all the
mostly latest development exist in one place, so I can be reasonably
sure the maintainer won't have trouble applying the patch on their tree
due to some missing patch, and if I work also on driver stuff, I can be
sure those drivers are also up-to-date-ish.
No, I don't think this patch specifically depends on anything in latest
next.
next prev parent reply other threads:[~2022-02-24 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 17:43 [PATCH v2] dt-bindings: leds: Document mmc trigger Marek Vasut
2022-02-24 22:31 ` Rob Herring
2022-02-24 23:08 ` Marek Vasut [this message]
2022-02-24 22:31 ` Rob Herring
2022-09-21 10:56 ` Pavel Machek
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=1e4dc8c2-daa7-3cef-eaf5-76616b6230a3@denx.de \
--to=marex@denx.de \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=pavel@ucw.cz \
--cc=robh@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).