linux-kernel - Re: [PATCH] ALSA: aoa: convert bus code to use dev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hoal34byh.wl-tiwai@suse.de>
Date:	Fri, 29 May 2015 17:53:26 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Quentin Lambert <lambert.quentin@...il.com>
Cc:	Johannes Berg <johannes@...solutions.net>,
	Jaroslav Kysela <perex@...ex.cz>,
	linuxppc-dev@...ts.ozlabs.org, alsa-devel@...a-project.org,
	linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] ALSA: aoa: convert bus code to use dev_groups

At Fri, 29 May 2015 17:49:06 +0200,
Quentin Lambert wrote:
> 
> 
> 
> On 28/05/2015 17:01, Takashi Iwai wrote:
> >>> Also, it'd be better to move ATTRIBUTE_GROUPS(soundbus_dev) into
> >>> soundbus/sysfs.c, and make it this global instead of
> >>> soundbus_dev_attrs[].
> >> Ok, I need to find a nice way to do that because ATTRIBUTE_GROUPS
> >> declares the
> >> structure as static.
> >
> > If it results in an ungly code, it's fine with the original code,
> > too.  But, maybe with a comment indicating that xxx_dev_attrs[] is
> > defined in xxx.c.
> >
> >
> Since sound/aoa/soundbus/sysfs is small, a solution would be
> to merge sound/aoa/soundbus/sysfs.c and sound/aoa/soundus/core.c.
> Moreover all 172 other usages of the ATTRIBUTE_GROUPS macro
> define the struct attribute *xxx_attrs[] in the same file
> they assign the .dev_groups field.
> 
> I'm not sure about this change as it seems way more important than
> adding a comment line as you suggested.

Not "important" but more "radical", I'd say.

> Should I send a patch merging these two files?

I don't think it's worth.  This is a fairly old hardware, thus the
code isn't so actively used/maintained.  Unless it looks too ugly, we
shouldn't touch too many things just for refactoring.

So, go for the way to have a minimum change.


thanks,

Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/