From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] Broken DM816x support in Linux 3.10-rc4
Date: Thu, 6 Jun 2013 08:55:41 -0700 [thread overview]
Message-ID: <20130606155541.GM3331@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306060414580.15042@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [130605 21:22]:
> Hi,
>
> also,
>
> On Wed, 5 Jun 2013, Aida Mynzhasova wrote:
>
> > Aida Mynzhasova (5):
> > ARM: OMAP: AM33xx: multiple renames for early initialization
>
> If this patch is what's responsible for all the file renaming, please drop
> it. Looks from the change summary that it's just useless churn (although
> I haven't seen the patch here since it never made it to the lists)
Yes no reason for all the renaming, marketing names can be
whatever. For example, we have am/dm37xx too which is really
omap36xx.
Regards,
Tony
prev parent reply other threads:[~2013-06-06 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 15:29 [PATCH 0/5] Broken DM816x support in Linux 3.10-rc4 Aida Mynzhasova
2013-06-05 15:29 ` [PATCH 1/5] ARM: OMAP: DM81xx: multiple renames for DM81xx platform Aida Mynzhasova
2013-06-05 15:29 ` [PATCH 3/5] ARM: OMAP: DM816x: add powerdomains for DM816x Aida Mynzhasova
2013-06-05 15:29 ` [PATCH 4/5] ARM: OMAP: DM816x: add clock domain support " Aida Mynzhasova
2013-06-05 15:29 ` [PATCH 5/5] ARM: OMAP: DM816x: add hwmod support for DM81xx Aida Mynzhasova
2013-06-06 3:54 ` [PATCH 0/5] Broken DM816x support in Linux 3.10-rc4 Paul Walmsley
2013-06-06 6:03 ` Aida Mynzhasova
2013-06-06 4:16 ` Paul Walmsley
2013-06-06 15:55 ` Tony Lindgren [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=20130606155541.GM3331@atomide.com \
--to=tony@atomide.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).