linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: haojian.zhuang@gmail.com (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] pxa: add namespace on ssp
Date: Thu, 1 Apr 2010 15:45:03 +0800	[thread overview]
Message-ID: <g2w771cded01004010045n56803dfbge90d3a70a731977d@mail.gmail.com> (raw)
In-Reply-To: <y2pf17812d71004010033x5b3e789foa782dd6cd8af63ef@mail.gmail.com>

On Thu, Apr 1, 2010 at 3:33 PM, Eric Miao <eric.y.miao@gmail.com> wrote:
> On Wed, Mar 31, 2010 at 8:46 PM, Haojian Zhuang
> <haojian.zhuang@gmail.com> wrote:
>> From b52a0d2687e82f81d38198cb450b6a39a9e53851 Mon Sep 17 00:00:00 2001
>> From: Haojian Zhuang <haojian.zhuang@marvell.com>
>> Date: Wed, 31 Mar 2010 15:08:55 -0400
>> Subject: [PATCH] [ARM] pxa: add namespace on ssp
>>
>> In order to prevent code ambiguous, add namespace on functions in ssp driver.
>>
>
> Haojian,
>
> This is not necessary, provided that those functions are static already.
> Unless this driver is going to support a different SSP, in which case a
> separate driver is needed then.
>
> What's the real motivation behind this?
>

It's the request from Mark. Both ssp_ and pxa_ssp_ prefix exist in
pxa-ssp.c. From the view of naming space, it's not align.

Thanks
Haojian

  reply	other threads:[~2010-04-01  7:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31 12:46 [PATCH 1/4] pxa: add namespace on ssp Haojian Zhuang
2010-04-01  7:33 ` Eric Miao
2010-04-01  7:45   ` Haojian Zhuang [this message]
2010-04-01  8:54     ` Mark Brown
2010-04-09 11:16 ` [alsa-devel] " Mark Brown
2010-04-16  3:54   ` Haojian Zhuang
2010-04-17  1:54     ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2010-04-17  5:34 Haojian Zhuang
2010-04-19 11:35 ` Liam Girdwood
2010-04-21 22:17 ` Eric Miao
2010-04-21 23:37   ` Mark Brown
2010-04-22  0:08   ` Mark Brown

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=g2w771cded01004010045n56803dfbge90d3a70a731977d@mail.gmail.com \
    --to=haojian.zhuang@gmail.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).