From: Quentin Lambert <lambert.quentin@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Jaroslav Kysela <perex@perex.cz>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH v2] ALSA: aoa: convert bus code to use dev_groups
Date: Fri, 12 Jun 2015 09:55:17 +0200 [thread overview]
Message-ID: <557A9065.5020608@gmail.com> (raw)
In-Reply-To: <s5heglil9de.wl-tiwai@suse.de>
On 11/06/2015 14:25, Takashi Iwai wrote:
> At Thu, 11 Jun 2015 14:04:45 +0200,
> Quentin Lambert wrote:
>>
>>
>> On 11/06/2015 12:02, Takashi Iwai wrote:
>>> At Thu, 11 Jun 2015 10:03:38 +0200,
>>> Quentin Lambert wrote:
>>>> The dev_attrs field of struct bus_type is going away, use dev_groups instead.
>>>> This converts the soundbus code to use the correct field.
>>>>
>>>> Given that all other usages of the macro define the struct attribute
>>>> *xxx_attrs[] in the same file they assign the .dev_groups field, this patch
>>>> merges sysfs.c into core.c.
>>>>
>>>> These modifications were made using Coccinelle.
>>>>
>>>> Signed-off-by: Quentin Lambert <lambert.quentin@gmail.com>
>>>> ---
>>>> Changes since v1:
>>>> - Fix the commit message to actually talk about soundbus rather than MDIO
>>>> - This version attempt to fix a problem resulting from the macro
>>>> ATTRIBUTE_GROUPS declaring the structure as static by merging sysfs.c into
>>>> core.c. I understand that this may not be the prefered solution since
>>>> Takashi suggested that adding a comment line to the previous version could
>>>> be acceptable.
>>> Hmm, the patch doesn't look as mentioned here.
>>> It's rather bigger than the previous patch. Is this intentional?
>>>
>> Well as mentionned in the change log it is bigger because it moves the
>> code from sysfs.c to
>> core.c. I realise as I am writing this that this patch should have
>> really been two patches.
>> The first one removing sysfs.c and the second one removing the use of
>> the dev_attrs.
> Yes, that'd be better. OTOH, do we really need to copy many codes at
> all? I really prefer shorter changes, if possible.
All right, I will send a third version following the comments you made
on the fist version. I just wanted to propose this idea in case it
suited you.
Quentin
next prev parent reply other threads:[~2015-06-12 7:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 12:48 [PATCH] ALSA: aoa: convert bus code to use dev_groups Quentin Lambert
2015-05-28 13:52 ` Takashi Iwai
2015-05-28 13:59 ` Quentin Lambert
2015-05-28 14:09 ` Takashi Iwai
2015-05-28 14:43 ` Quentin Lambert
2015-05-28 15:01 ` Takashi Iwai
2015-05-29 15:49 ` Quentin Lambert
2015-05-29 15:53 ` Takashi Iwai
2015-05-28 13:59 ` Quentin Lambert
2015-06-11 8:03 ` [PATCH v2] " Quentin Lambert
2015-06-11 10:02 ` [alsa-devel] " Takashi Iwai
2015-06-11 12:04 ` Quentin Lambert
2015-06-11 12:25 ` Takashi Iwai
2015-06-12 7:55 ` Quentin Lambert [this message]
2015-06-11 11:55 ` walter harms
2015-06-11 12:06 ` Quentin Lambert
2015-06-12 8:38 ` [PATCH v3] " Quentin Lambert
2015-06-12 9:59 ` Andreas Schwab
2015-06-12 10:01 ` Quentin Lambert
2015-06-12 18:50 ` Takashi Iwai
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=557A9065.5020608@gmail.com \
--to=lambert.quentin@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=johannes@sipsolutions.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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).