From: Lee Jones <lee.jones@linaro.org>
To: Luiz Sampaio <sampaio.ime@gmail.com>
Cc: daniel.thompson@linaro.org, michael.hennerich@analog.com,
jingoohan1@gmail.com, deller@gmx.de,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 24/31] video: backlight: changing LED_* from enum led_brightness to actual value
Date: Mon, 24 Jan 2022 10:53:13 +0000 [thread overview]
Message-ID: <Ye6FGUPJ7KH5gYdf@google.com> (raw)
In-Reply-To: <20220121180948.2501-1-sampaio.ime@gmail.com>
On Fri, 21 Jan 2022, Luiz Sampaio wrote:
> Hello, Daniel
>
> Thanks for your reply. This is one of my first patches, so I am still
> learning. This series of patches affects others subsystems too (hid,
> leds, sound etc). Should I create series for each subsystem
> separately, instead of creating one series for everyone?
> What do you mean by "this patch might wants to land in one tree"?
Can the individual patches be applied on their own without causing
issues (warnings/errors) with the build? If so, they can be applied
separately via their associated subsystem trees. If not, someone will
have to collect them all and take them via a single tree with Acks
from the other subsystem maintainers.
It's difficult to make that decision for ourselves since you didn't
share all of the patches with all of the maintainers.
--
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2022-01-24 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220121165436.30956-1-sampaio.ime@gmail.com>
2022-01-21 16:54 ` [PATCH 24/31] video: backlight: changing LED_* from enum led_brightness to actual value Luiz Sampaio
2022-01-21 17:05 ` Daniel Thompson
2022-01-21 18:06 ` Luiz Sampaio
2022-01-21 18:09 ` Luiz Sampaio
2022-01-24 10:53 ` Lee Jones [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=Ye6FGUPJ7KH5gYdf@google.com \
--to=lee.jones@linaro.org \
--cc=daniel.thompson@linaro.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=sampaio.ime@gmail.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;
as well as URLs for NNTP newsgroup(s).