linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lho@apm.com (Loc Ho)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2 RESEND] power: reset: Add syscon reboot/poweroff device nodes for APM X-Gene platform
Date: Wed, 22 Jul 2015 10:46:36 -0700	[thread overview]
Message-ID: <CAPw-ZT=d2=dh-Hjugo9BStCuhTp82MMapUa1EGrD01EoTOG-nA@mail.gmail.com> (raw)
In-Reply-To: <20150714084004.GA14593@localhost>

Hi Olof,

>> This patch set adds syscon reboot/poweroff device nodes to support reboot and
>> poweroff features on X-Gene platform.
>>
>> Tai Nguyen (2):
>>   power: reset: Add syscon reboot device node for APM X-Gene platform
>>   power: reset: Add syscon poweroff device node for APM X-Gene Mustang platform
>>
>>  arch/arm64/boot/dts/apm/apm-mustang.dts |   12 ++++++++++++
>>  arch/arm64/boot/dts/apm/apm-storm.dtsi  |   12 ++++++++++++
>>  2 files changed, 24 insertions(+)
>
> Hi,
>
> It's unclear to me what you want to happen to these patches. They are
> sent to a long list of to-recipients, one of which is arm at kernel.org. In
> general, specify the person you want to take action on the patch in to
> with the rest on cc.

Is there an owner for all DT node files? Is that Catalina as he is
owner for ARM64 arch folder?

>
> We generally ask that patches first go to the subarch maintainers,
> and they in turn send it on to us (either through a pull request or
> by sending the patches to be applied). In the case of X-Gene, there is
> no general platform maintainer so we keep getting patches from various
> engineers at APM and it's unclear to us what your intentions are.
>
> I'd prefer to see one (to start with) person in charge of these (i.e. one
> maintainer from the APM side). Please add that person to the MAINTAINERS
> file as well.

Are you suggesting that we have one person to start an GIT with
kernel.org to keep all these misc ack'ed patches for X-Gene (APM) that
don't seems to have an maintainer/home. Then request an pull by you?

Thanks,
Loc

  reply	other threads:[~2015-07-22 17:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 19:19 [PATCH 0/2 RESEND] power: reset: Add syscon reboot/poweroff device nodes for APM X-Gene platform Tai Nguyen
2015-06-02 19:19 ` [PATCH 1/2 RESEND] power: reset: Add syscon reboot device node " Tai Nguyen
2015-06-09 15:32   ` Dann Frazier
2015-06-02 19:19 ` [PATCH 2/2 RESEND] power: reset: Add syscon poweroff " Tai Nguyen
2015-06-09  3:44   ` Dann Frazier
2015-06-09  4:34     ` Tai Tri Nguyen
2015-06-09 15:31       ` Dann Frazier
2015-06-09 16:47         ` Tai Tri Nguyen
2015-06-10 19:13         ` Dann Frazier
2015-06-10 23:00           ` Moritz Fischer
2015-07-14  8:40 ` [PATCH 0/2 RESEND] power: reset: Add syscon reboot/poweroff device nodes " Olof Johansson
2015-07-22 17:46   ` Loc Ho [this message]
2015-07-22 17:52     ` Olof Johansson
2015-07-22 18:10       ` Loc Ho
2015-07-22 18:20         ` Olof Johansson
2015-07-25 18:34           ` Duc Dang
2015-07-26 18:37             ` Olof Johansson
2015-07-28 17:51               ` Duc Dang
2015-08-28 20:00               ` Duc Dang
2015-08-28 20:06                 ` Olof Johansson

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='CAPw-ZT=d2=dh-Hjugo9BStCuhTp82MMapUa1EGrD01EoTOG-nA@mail.gmail.com' \
    --to=lho@apm.com \
    --cc=linux-arm-kernel@lists.infradead.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).