netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Paulius Zaleckas <paulius.zaleckas@teltonika.lt>
Cc: linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: remove special ioctl from hso driver, replace by rfkill
Date: Thu, 17 Apr 2008 15:39:29 -0700	[thread overview]
Message-ID: <20080417223929.GA31384@kroah.com> (raw)
In-Reply-To: <4807C42F.9050409@teltonika.lt>

On Fri, Apr 18, 2008 at 12:42:07AM +0300, Paulius Zaleckas wrote:
> Oliver Neukum wrote:
>>  /* called once for each interface upon device insertion */
>>  static int hso_probe(struct usb_interface *interface,
>>  		     const struct usb_device_id *id)
>>  {
>>  	int mux, i, if_num, port_spec;
>>  	unsigned char port_mask;
>> +	char *rfkn;
>>  	struct hso_device *hso_dev = NULL;
>>  	struct hso_shared_int *shared_int = NULL;
>>  	struct hso_device *tmp_dev = NULL;
>> @@ -2747,6 +2706,27 @@ static int hso_probe(struct usb_interfac
>>  		goto exit;
>>  	}
>>  +	hso_dev->rfkill = rfkill_allocate(&interface_to_usbdev(interface)->dev,
>> +				RFKILL_TYPE_WLAN);
>
> What will happen if rfkill is not enabled on kernel? I think HSO should
> not depend on rfkill. Solution should be to do #ifdef CONFIG_RFKILL..?

Ick, rfkill should degrade properly so that #ifdefs are not needed here.
I'll fix up rfkill.h to prevent this kind of dependancy requirement.

thanks,

greg k-h

  reply	other threads:[~2008-04-17 22:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16 12:28 remove special ioctl from hso driver, replace by rfkill Oliver Neukum
2008-04-16 13:06 ` Paulius Zaleckas
     [not found]   ` <4805F9DB.5030004-Ft0m5Q12RQ9xBelEqimL3w@public.gmane.org>
2008-04-16 13:53     ` Oliver Neukum
2008-04-17 21:42 ` Paulius Zaleckas
2008-04-17 22:39   ` Greg KH [this message]
2008-04-17 23:28     ` Marcel Holtmann
     [not found] ` <200804161428.18066.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2008-04-17 21:43   ` Greg KH
2008-04-18 13:56   ` Paulius Zaleckas
2008-04-18 16:25     ` Greg KH
2008-04-21  8:47       ` Paulius Zaleckas

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=20080417223929.GA31384@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulius.zaleckas@teltonika.lt \
    /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).