From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] MAINTAINERS: add more files under OMAP SUPPORT
Date: Mon, 10 Nov 2014 09:03:09 -0800 [thread overview]
Message-ID: <20141110170309.GK31454@atomide.com> (raw)
In-Reply-To: <1415284639-6951-1-git-send-email-balbi@ti.com>
* Felipe Balbi <balbi@ti.com> [141106 06:38]:
> These files are very important to the healt
> of the OMAP architecture, specially when it
> comes to PM support which currently we have
> working for at least OMAP3 and we'd like
> to know about any changes being made to our
> PMICs and IRQ controllers.
Applying into omap-for-v3.18/fixes as this is
already a bit of problem.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] MAINTAINERS: add more files under OMAP SUPPORT
Date: Mon, 10 Nov 2014 09:03:09 -0800 [thread overview]
Message-ID: <20141110170309.GK31454@atomide.com> (raw)
In-Reply-To: <1415284639-6951-1-git-send-email-balbi@ti.com>
* Felipe Balbi <balbi@ti.com> [141106 06:38]:
> These files are very important to the healt
> of the OMAP architecture, specially when it
> comes to PM support which currently we have
> working for at least OMAP3 and we'd like
> to know about any changes being made to our
> PMICs and IRQ controllers.
Applying into omap-for-v3.18/fixes as this is
already a bit of problem.
Regards,
Tony
next prev parent reply other threads:[~2014-11-10 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 14:37 [PATCH v2] MAINTAINERS: add more files under OMAP SUPPORT Felipe Balbi
2014-11-06 14:37 ` Felipe Balbi
2014-11-10 17:03 ` Tony Lindgren [this message]
2014-11-10 17:03 ` Tony Lindgren
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=20141110170309.GK31454@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.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.