All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Explicitly disable BT radio using rfkill interface on
Date: Tue, 14 Jul 2009 21:20:24 +0000	[thread overview]
Message-ID: <1247606424.4549.28.camel@violet> (raw)
In-Reply-To: <4A4A8B6D.3060509@dell.com>

Hi Mario,

> I'll switch over to one line.  I had thought it was more readable as
> multiline.
> Since the rule is referring to the parent's information, I wasn't sure
> that this was doable without importing the properties of the parent's
> earlier rules. 

what is wrong with using ATTRS here?

> > That whole thing get pretty annoying, it does not seem to be ready to
> > be shipped with udev. 
> > Please properly fix _and_ test the stuff now.
> > Your earlier version already broke random keyboards and hubs, because
> > you obviously did not test it properly. If you don't provide a sane
> > solution now, I'm going to remove it from udev, and you need to create
> > your own package.
> >   
> The utility itself is stable.  The previous error with the matching
> against hubs within docking stations was something I didn't anticipate
> matching up the chain, indeed my mistake.  It was corrected by being
> more specific on things to match on, which is what I am attempting
> again with this second rule.  
> 
> Attached is an updated patch.  Again, i'm having to rely on earlier
> rules for parent device information.  If there is a better way to do
> this, can you please advise rather than be rash about removing this
> utility from udev?  There shouldn't be any worry for mismatching
> devices this time.  The new rule looks specifically for Dell Wireless
> Class Controllers, with a Bluetooth protocol not matching further up
> the chain.
> 
> I broke up the for loops by relying on find_device instead.  My code
> is quite similar to the example that is on the libusb documentation
> for matching a property:
> http://libusb.sourceforge.net/doc/examples-code.html
> I'm not really sure of any way to make it more readable other than
> adding superfluous spacing and comments as it's a very basic example.

Split more up into proper matching functions and with extra variables to
pointers. This is still unreadable.

Regards

Marcel



  parent reply	other threads:[~2009-07-14 21:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 22:02 [PATCH] Explicitly disable BT radio using rfkill interface on Mario Limonciello
2009-06-30 22:26 ` Kay Sievers
2009-07-01  3:53 ` [PATCH] Explicitly disable BT radio using rfkill interface on suspend Mario_Limonciello
2009-07-01 12:06 ` [PATCH] Explicitly disable BT radio using rfkill interface on Marcel Holtmann
2009-07-01 13:13 ` [PATCH] Explicitly disable BT radio using rfkill interface on suspend Mario_Limonciello
2009-07-01 15:03 ` [PATCH] Explicitly disable BT radio using rfkill interface on Marcel Holtmann
2009-07-01 17:12 ` Mario Limonciello
2009-07-01 17:18 ` Matthew Garrett
2009-07-01 22:13 ` Marcel Holtmann
2009-07-01 22:16 ` Matthew Garrett
2009-07-01 22:23 ` Mario Limonciello
2009-07-01 22:49 ` Marcel Holtmann
2009-07-01 22:52 ` Matthew Garrett
2009-07-02 14:02 ` Alan Stern
2009-07-10 14:46 ` Alan Stern
2009-07-14 16:40 ` Mario Limonciello
2009-07-14 16:51 ` Alan Stern
2009-07-14 16:52 ` Kay Sievers
2009-07-14 17:32 ` Mario Limonciello
2009-07-14 18:46 ` Marcel Holtmann
2009-07-14 19:12 ` Kay Sievers
2009-07-14 21:00 ` Mario Limonciello
2009-07-14 21:20 ` Marcel Holtmann [this message]
2009-07-14 21:24 ` Kay Sievers
2009-07-14 22:45 ` Kay Sievers
2009-07-15  2:07 ` Alan Stern
2009-07-15  2:26 ` Kay Sievers
2009-07-15 22:15 ` Mario Limonciello
2009-07-15 22:24 ` Mario Limonciello
2009-07-15 23:27 ` Kay Sievers

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=1247606424.4549.28.camel@violet \
    --to=marcel@holtmann.org \
    --cc=linux-hotplug@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.