From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Olof Johansson <olof@lixom.net>
Cc: Kumar Gala <galak@codeaurora.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Use of drivers/platform and matching include?
Date: Thu, 3 Oct 2013 10:09:14 -0700 [thread overview]
Message-ID: <20131003170914.GA11992@kroah.com> (raw)
In-Reply-To: <CAOesGMjJ6Uj0uGFJqtnWQyDW+tr6eLVWoHZ+B7uFna+L8N6E8Q@mail.gmail.com>
On Thu, Oct 03, 2013 at 09:46:30AM -0700, Olof Johansson wrote:
> I don't have a good answer though. If it wasn't for the arm64 fork,
> locating these under arch/arm somewhere would really be the reasonable
> answer, like we used to do on powerpc. :(
Sounds like yet-another-good reason why there shouldn't be an arm64
"fork" at all :(
The arm community created this mess, you all can fix it up, it's not too
late.
greg k-h
next prev parent reply other threads:[~2013-10-03 17:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 14:45 Use of drivers/platform and matching include? Kumar Gala
2013-10-03 15:27 ` Greg Kroah-Hartman
2013-10-03 16:21 ` Kumar Gala
2013-10-03 16:25 ` Greg Kroah-Hartman
2013-10-03 16:38 ` Kumar Gala
2013-10-03 16:46 ` Olof Johansson
2013-10-03 17:09 ` Greg Kroah-Hartman [this message]
2013-10-03 17:54 ` Olof Johansson
2013-10-04 11:18 ` Catalin Marinas
2013-10-04 11:50 ` Russell King - ARM Linux
2013-10-04 11:43 ` Russell King - ARM Linux
2013-10-04 12:03 ` Catalin Marinas
2013-10-04 11:41 ` Russell King - ARM Linux
2013-10-04 13:22 ` Greg Kroah-Hartman
2013-10-04 16:48 ` Olof Johansson
2013-10-04 19:29 ` Santosh Shilimkar
2013-10-05 17:13 ` Greg Kroah-Hartman
2013-10-08 0:26 ` Rohit Vaswani
2013-10-08 2:19 ` Greg Kroah-Hartman
2013-10-07 6:48 ` Andi Shyti
2013-10-08 17:57 ` Rohit Vaswani
2013-10-09 6:04 ` Andi Shyti
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=20131003170914.GA11992@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=galak@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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).