linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kumar Gala <galak@codeaurora.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: Use of drivers/platform and matching include?
Date: Thu, 3 Oct 2013 09:25:19 -0700	[thread overview]
Message-ID: <20131003162519.GA25042@kroah.com> (raw)
In-Reply-To: <B674A07C-F8FE-4F4D-BB0A-87D5A50852D0@codeaurora.org>

On Thu, Oct 03, 2013 at 11:21:10AM -0500, Kumar Gala wrote:
> 
> On Oct 3, 2013, at 10:27 AM, Greg Kroah-Hartman wrote:
> 
> > On Thu, Oct 03, 2013 at 09:45:38AM -0500, Kumar Gala wrote:
> >> As we look at upstreaming more support for the Qualcomm MSM SoCs there
> >> are a number of drivers or library like routines that are unique to
> >> the MSM platform, we are thinking that putting them under:
> >> 
> >> drivers/platform/qcom/
> > 
> > What type of drivers are these?  Shouldn't they really go under the
> > specific driver type directory instead?
> 
> If there isn't an existing driver/ dir for this I dont see how it can go there, I'm not also not really a fan of trying to artificial put something that is highly SoC specific into something generic of this nature.

Loose a line-wrap somewhere?...

Anyway, you didn't answer my question, so why do I need to answer yours?

snarkily,

greg k-h

  reply	other threads:[~2013-10-03 16:25 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 [this message]
2013-10-03 16:38       ` Kumar Gala
2013-10-03 16:46 ` Olof Johansson
2013-10-03 17:09   ` Greg Kroah-Hartman
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=20131003162519.GA25042@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 \
    /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).