From: David Brown <davidb@codeaurora.org>
To: linux-kernel@vger.kernel.org
Cc: Dima Zavin <dima@android.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Daniel Walker <dwalker@fifo99.com>,
Kenneth Heitke <kheitke@codeaurora.org>,
linux-arm-msm@vger.kernel.org, tsoni@codeaurora.org,
linux-arm-kernel@lists.infradead.org, swetland@google.com
Subject: Re: [PATCH v2 2/2] msm: add single-wire serial bus interface (SSBI) driver
Date: Thu, 24 Feb 2011 19:20:45 -0800 [thread overview]
Message-ID: <8ya8vx4dcky.fsf@huya.qualcomm.com> (raw)
In-Reply-To: <AANLkTikD1Ued=rit1QbMWwe3NGFz2iQ-KO7B=-N6Ok-2@mail.gmail.com> (Dima Zavin's message of "Thu, 24 Feb 2011 18:39:48 -0800")
On Thu, Feb 24 2011, Dima Zavin wrote:
> On that note, should we have a "drivers/arm/msm" instead of just
> "drivers/msm"? Other non-msm arm sub-arches probably have the same
> problem and polluting drivers/ top-level for every arm-subarch maybe
> undesirable.
I'm moving linux-kernel to the 'to' field, and adding Greg KH to CC.
This is about a new driver (ssbi) for the MSM chips, and where the
driver for this should go. The driver is specific to MSM chips (as far
as I know, the bus is only supported there). There are likely to be
future msm-specific drivers, so the suggestion was to put this under
drivers/msm, or possibly drivers/arm/msm.
Anyone other suggestions, or preferences for the location?
Thanks,
David Brown
next prev parent reply other threads:[~2011-02-25 3:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1298585954-22422-1-git-send-email-kheitke@codeaurora.org>
2011-02-24 22:19 ` [PATCH v2 1/2] MAINTAINERS: Add drivers/msm to MSM subsystem Kenneth Heitke
2011-02-24 23:08 ` Nicolas Pitre
2011-02-24 22:19 ` [PATCH v2 2/2] msm: add single-wire serial bus interface (SSBI) driver Kenneth Heitke
2011-02-25 2:23 ` Daniel Walker
2011-02-25 2:31 ` David Brown
2011-02-25 2:35 ` Daniel Walker
2011-02-25 2:39 ` Dima Zavin
2011-02-25 3:20 ` David Brown [this message]
2011-02-25 3:28 ` Greg KH
2011-02-25 3:54 ` David Brown
2011-02-25 3:58 ` Greg KH
2011-02-25 4:06 ` David Brown
2011-02-25 19:00 ` David Brown
2011-02-25 20:21 ` Brian Swetland
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=8ya8vx4dcky.fsf@huya.qualcomm.com \
--to=davidb@codeaurora.org \
--cc=dima@android.com \
--cc=dwalker@fifo99.com \
--cc=gregkh@suse.de \
--cc=kheitke@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swetland@google.com \
--cc=tsoni@codeaurora.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