mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: xiphmont@xiph.org
Cc: "Pierre Ossman" <drzeus@drzeus.cx>,
	fedora-desktop-list@redhat.com, alsa-devel@alsa-project.org,
	jrb@redhat.com, "Greg KH" <greg@kroah.com>,
	linux-kernel@vger.kernel.org, mclasen@redhat.com,
	"Lennart Poettering" <lennart@poettering.net>,
	perex@suse.cz
Subject: Re: [Alsa-devel] [PATCH] alsa: correct nonsensical sysfs device symlinks
Date: Thu, 25 Jan 2007 19:38:48 +0100	[thread overview]
Message-ID: <s5h1wljuf2f.wl%tiwai@suse.de> (raw)
In-Reply-To: <806dafc20701251034l59fc5be7ta881606046eb819a@mail.gmail.com>

At Thu, 25 Jan 2007 13:34:19 -0500,
xiphmont@xiph.org wrote:
> 
> On 1/25/07, Takashi Iwai <tiwai@suse.de> wrote:
> 
> > The problem with your patch is that it breaks the structure newly
> > introduced.  In the new tree, card* contains the whole belonging
> > devices, and each device points to the one in the card object.
> > Passing dev->parent there cuts the relation between the card object
> > and each device.
> >
> > That's why my patch rules out setting card->dev with ifdef
> > CONFIG_SYSFS_DEPRECATED.  As fallback, it takes the parent device to
> > build the old style tree.
> >
> > > Having just checked a 2.6.18 machine, none of the device symlinks
> > > point to card* objects; thay all point to /sys/devices/....
> >
> > Yes, it's a new stuff.
> 
> [This does beg the question: Does the benefit of this complete
> restructuring in a subminor release of an allegedly stable kernel
> outweigh the fact that it breaks all audio for any user running a
> gnome desktop?]

Well, that's not me who introduced that ;)

> OK, so my patch should be passing card->parent or dev->parent only in
> the case that CONFIG_SYSFS_DEPRECATED is set, and leaving the call the
> way it was previously in the case CONFIG_SYSFS_DEPRECATED is not set.
> Essentially, ifdef/else both cases?

Also, avoid creating card* instance.  It makes no sense in that case.
(So... what's wrong with my patch?)

> Is this also going to have to be the case for every other class type
> that converts from class_device_create to device_create?

I don't think so.  The case of sound class is more complicated, a
combination of API change and a new tree.


Takashi

  reply	other threads:[~2007-01-25 18:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25  1:50 Christopher "Monty" Montgomery
2007-01-25  4:26 ` Greg KH
2007-01-25 14:11   ` Christopher "Monty" Montgomery
2007-01-25 15:15     ` Pierre Ossman
2007-01-25 15:36       ` Christopher "Monty" Montgomery
2007-01-25 15:40         ` Pierre Ossman
2007-01-25 15:57           ` Christopher "Monty" Montgomery
2007-01-25 16:54             ` [Alsa-devel] " Takashi Iwai
2007-01-25 17:03               ` Christopher "Monty" Montgomery
2007-01-25 17:30                 ` xiphmont
2007-01-25 17:47                   ` Takashi Iwai
2007-01-25 18:07                     ` xiphmont
2007-01-25 18:23                       ` Takashi Iwai
2007-01-25 18:34                         ` xiphmont
2007-01-25 18:38                           ` Takashi Iwai [this message]
2007-01-25 18:51                             ` xiphmont
2007-01-25 19:49                               ` Greg KH
2007-01-25 20:40                                 ` xiphmont
2007-01-25 21:59                                   ` Greg KH
2007-01-26 10:53                                     ` xiphmont
2007-01-26 11:40                                       ` Takashi Iwai
2007-01-26 18:04                                         ` Greg KH
2007-01-26 18:25                                           ` Takashi Iwai
2007-01-26 18:31                                             ` xiphmont
2007-01-26 19:06                                             ` Greg KH
2007-01-26 21:58                                               ` xiphmont
2007-01-26 18:03                                     ` xiphmont
2007-01-26 18:42                                       ` Greg KH
2007-01-25 17:48                   ` Christopher "Monty" Montgomery
2007-01-25 11:27 ` Pierre Ossman

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=s5h1wljuf2f.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=drzeus@drzeus.cx \
    --cc=fedora-desktop-list@redhat.com \
    --cc=greg@kroah.com \
    --cc=jrb@redhat.com \
    --cc=lennart@poettering.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mclasen@redhat.com \
    --cc=perex@suse.cz \
    --cc=xiphmont@xiph.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

all inboxes | Powered by JetHome®