From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Petr Cvek <petr.cvek@tul.cz>, Philipp Zabel <philipp.zabel@gmail.com>
Cc: Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>, Bryan Wu <cooloney@gmail.com>,
Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <j.anaszewski@samsung.com>,
Russell King <linux@arm.linux.org.uk>,
Sebastian Reichel <sre@kernel.org>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org, linux-leds@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v1 RFC] This patch repairs HTC Magician machine (PXA27x) support
Date: Thu, 13 Aug 2015 20:01:08 +0200 [thread overview]
Message-ID: <87y4hfhxuj.fsf@belgarion.home> (raw)
In-Reply-To: <55CBCDED.8010409@tul.cz> (Petr Cvek's message of "Thu, 13 Aug 2015 00:51:25 +0200")
Petr Cvek <petr.cvek@tul.cz> writes:
> Fixing original code: Problems to successful boot due to the bad LCD
> power sequence (wrongly configured GPIO).
>
> Add/fix platform data and helper function for various hardware
> (touchscreen, audio, USB device, ...).
>
> Add new discovered GPIOs and fix names by GPIO context.
>
> Add new LEDs driver.
>
> Signed-off-by: Petr Cvek <petr.cvek@tul.cz>
Hi Petr,
Just as Lee, I want the serie to be split per-subsystem.
For the mach-pxa part, I need you to split the patch into several chunks to
review.
At least please split :
- a first patch for cleanup (identation and whitespaces)
- a second patch for cleanup (comments changes, debug messages)
- a serie of fix patches
- one for the power sequence
- one for GPIO fixes
- a serie of evolution patches
- new gpio_keys
- new backlight stuff
- one per new device declared
- new flash stuff
- etc ...
Please keep in mind that in order to pick the patches, I need to split them in 3
groups :
- cleanups
- fixes
- evolutions / new stuff
Moreover I want to be able to revert one functionality (for example new power
sequence) without reverting the whole serie.
You probably know that the pxa patches need the subject prefix to be "ARM: pxa:
magician: " in your case. Other subsystem maintainers have similar requirements
I believe.
When that's done, I'll begin the review, and Philipp will probably too as he is
the maintainer.
Cheers.
--
Robert
prev parent reply other threads:[~2015-08-13 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 22:51 [PATCH v1 RFC] This patch repairs HTC Magician machine (PXA27x) support Petr Cvek
2015-08-12 23:10 ` Petr Cvek
2015-08-13 8:10 ` Jacek Anaszewski
2015-08-13 8:17 ` Lee Jones
2015-08-13 18:01 ` Robert Jarzmik [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=87y4hfhxuj.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=cooloney@gmail.com \
--cc=daniel@zonque.org \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=haojian.zhuang@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=petr.cvek@tul.cz \
--cc=philipp.zabel@gmail.com \
--cc=rpurdie@rpsys.net \
--cc=sameo@linux.intel.com \
--cc=sre@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