All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Zhao Qiang-B45475 <qiang.zhao@freescale.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	Xie Xiaobo-R63061 <X.Xie@freescale.com>
Subject: Re: qe: move qe from arch/powerpc to drivers
Date: Thu, 7 Aug 2014 12:15:05 -0500	[thread overview]
Message-ID: <1407431705.7427.53.camel@snotra.buserror.net> (raw)
In-Reply-To: <4fff14ebe11b44e997bbdc75f240356b@BLUPR03MB341.namprd03.prod.outlook.com>

On Thu, 2014-08-07 at 04:15 -0500, Zhao Qiang-B45475 wrote:
> On Thu, Aug 7, 2014 at 4:16 AM, Wood Scott wrote:
> 
> 
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Thursday, August 07, 2014 4:16 AM
> > To: Zhao Qiang-B45475
> > Cc: linuxppc-dev@lists.ozlabs.org; Xie Xiaobo-R63061
> > Subject: Re: qe: move qe from arch/powerpc to drivers
> > 
> > On Wed, 2014-08-06 at 03:53 -0500, Zhao Qiang-B45475 wrote:
> > > On Wed, Jul 30, 2014 at 08:19 AM, Wood Scott wrote:
> > >
> > >
> > > > -----Original Message-----
> > > > From: Wood Scott-B07421
> > > > Sent: Wednesday, July 30, 2014 8:19 AM
> > > > To: Zhao Qiang-B45475
> > > > Cc: linuxppc-dev@lists.ozlabs.org; Wood Scott-B07421; Xie
> > > > Xiaobo-R63061
> > > > Subject: Re: qe: move qe from arch/powerpc to drivers
> > > >
> > > > On Tue, Jun 24, 2014 at 11:31:52AM +0800, Zhao Qiang wrote:
> > > > > ls1 has qe and ls1 has arm cpu.
> > > > > move qe from arch/powerpc to drivers.
> > > > >
> > > > > Signed-off-by: Zhao Qiang <B45475@freescale.com>
> > > >
> > > > This is a very terse changelog.  Explain more about what QE is, and
> > > > what this patch accomplishes (it doesn't seem to get rid of the PPC
> > > > dependency, just moving code at this stage)
> > > >
> > > > I don't see a MAINTAINERS update for the new path.  Who is going to
> > > > maintain it?
> > > >
> > > > I don't think drivers/qe is the right place for it.  Directories
> > > > directly under drivers/ tend to be for classes of devices, not
> > > > instances.  In any case, LKML should be CCed when creating a new
> > > > directory directly under drivers/ or under a subdirectory of
> > > > drivers/ that doesn't have its own mailing list.
> > >
> > > So which directory do you recommend?
> > 
> > drivers/soc/
> > 
> > > Actually qe is a kind of IP block, so in my opinion, it is proper to
> > put it under driver/(just in my opinion).
> > 
> > No, it isn't a type of device (e.g. "ethernet" or "tty").  It's an
> > abbreviation of a trademark for a specific multipurpose I/O architecture.
> 
> So which directory do you recommend?

Please see about 10 lines up. :-P

-Scott

  reply	other threads:[~2014-08-07 17:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24  3:31 [PATCH] qe: move qe from arch/powerpc to drivers Zhao Qiang
2014-07-30  0:19 ` Scott Wood
2014-08-06  8:53   ` qiang.zhao
2014-08-06 20:15     ` Scott Wood
2014-08-07  9:15       ` qiang.zhao
2014-08-07 17:15         ` Scott Wood [this message]
2014-08-07 18:57     ` Timur Tabi
2014-08-07 20:08       ` Scott Wood
2014-08-07 20:09         ` Timur Tabi
2014-08-07 20:11           ` Scott Wood
2014-08-07 20:13             ` Timur Tabi

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=1407431705.7427.53.camel@snotra.buserror.net \
    --to=scottwood@freescale.com \
    --cc=X.Xie@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=qiang.zhao@freescale.com \
    /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.