Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org, clemens@ladisch.de
Subject: Re: [PATCH 0/6] ALSA: firewire: simplify symbol space for local linkage
Date: Wed, 04 Jan 2017 11:39:11 +0100	[thread overview]
Message-ID: <s5hpok3qfcg.wl-tiwai@suse.de> (raw)
In-Reply-To: <387d35ad-0261-689f-8680-af68351d87a6@sakamocchi.jp>

On Wed, 04 Jan 2017 11:36:10 +0100,
Takashi Sakamoto wrote:
> 
> Hi,
> 
> On Jan 4 2016 03:43, Takashi Iwai wrote:
> > On Tue, 03 Jan 2017 13:41:15 +0100,
> > Takashi Sakamoto wrote:
> >>
> >> Hi,
> >>
> >> This patchset is just for code improvements, without adding features.
> >>
> >> Modules in ALSA firewire stack have some implementations for operation
> >> structures which sound subsystem defines. All of them are referred just by
> >> each local function to register corresponding operations. In this case, it's
> >> better to put them into the function local so that symbol space in local
> >> linkage of translation unit is kept to be simple.
> >
> > Do we see any merit in the resultant binaries by these changes?
> > I'm not against this kind of code changes, but just wondered.
> > That is, it's not totally clear what you takes as really "better" in
> > your context.
> 
> Mmm, sorry but my explanation is wrong. I managed to describe the
> reason in an aspect of local linkage, but an aim of this patchset is
> irrelevant to it.
> 
> The aim is for identifier space of each translation unit. The merit
> can be described in two points:
>  - For readers
>   - readers have no concern about where the identifier is referred.
>     It's just inner the including function.
>  - For identifier space of the file
>   - developers are free from name conflict for further work.
> 
> If no objections against the aim, I'll resubmit this patchset with
> proper commit comments.

Yes, please go ahead.


thanks,

Takashi

      reply	other threads:[~2017-01-04 10:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 12:41 [PATCH 0/6] ALSA: firewire: simplify symbol space for local linkage Takashi Sakamoto
2017-01-03 12:41 ` [PATCH 1/6] ALSA: bebob: " Takashi Sakamoto
2017-01-03 12:41 ` [PATCH 2/6] ALSA: fireworks: " Takashi Sakamoto
2017-01-03 12:41 ` [PATCH 3/6] ALSA: oxfw: " Takashi Sakamoto
2017-01-03 12:41 ` [PATCH 4/6] ALSA: dice: " Takashi Sakamoto
2017-01-03 12:41 ` [PATCH 5/6] ALSA: firewire-digi00x: " Takashi Sakamoto
2017-01-03 12:41 ` [PATCH 6/6] ALSA: firewire-tascam: " Takashi Sakamoto
2017-01-03 18:43 ` [PATCH 0/6] ALSA: firewire: " Takashi Iwai
2017-01-04 10:36   ` Takashi Sakamoto
2017-01-04 10:39     ` Takashi Iwai [this message]

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=s5hpok3qfcg.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=o-takashi@sakamocchi.jp \
    /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