From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Tuttle <ttuttle@chromium.org>
Cc: linux-serial@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 2/4] qcserial: log when an interface has too many altsettings
Date: Wed, 1 Feb 2012 13:11:16 -0800 [thread overview]
Message-ID: <20120201211116.GA30758@kroah.com> (raw)
In-Reply-To: <20120201210723.GB16802@google.com>
On Wed, Feb 01, 2012 at 04:07:23PM -0500, Thomas Tuttle wrote:
> Signed-off-by: Thomas Tuttle <ttuttle@chromium.org>
> ---
> drivers/usb/serial/qcserial.c | 6 +++++-
> 1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/usb/serial/qcserial.c b/drivers/usb/serial/qcserial.c
> index 26e3e30..5a817d6 100644
> --- a/drivers/usb/serial/qcserial.c
> +++ b/drivers/usb/serial/qcserial.c
> @@ -145,8 +145,12 @@ static int qcprobe(struct usb_serial *serial, const struct usb_device_id *id)
> /* Gobi 2000 has a single altsetting, older ones have two */
> if (serial->interface->num_altsetting == 2)
> intf = &serial->interface->altsetting[1];
> - else if (serial->interface->num_altsetting > 2)
> + else if (serial->interface->num_altsetting > 2) {
> + dev_err(&serial->dev->dev,
> + "too many altsettings: %u",
> + serial->interface->num_altsetting);
Why would this happen? And what does spitting out an error do about it?
What are we supposed to do with this information?
thanks,
greg k-h
next prev parent reply other threads:[~2012-02-01 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 21:07 [PATCH 2/4] qcserial: log when an interface has too many altsettings Thomas Tuttle
2012-02-01 21:11 ` Greg KH [this message]
[not found] ` <20120201211116.GA30758-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-02-01 21:47 ` ttuttle
2012-02-01 22:02 ` Greg KH
2012-02-01 22:15 ` ttuttle
[not found] ` <CADyrwZQNMpxh5yTBnH68+0KK9r5NFvFMgad1K8qXouWAHY=1Rg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-01 22:23 ` Greg KH
2012-02-01 22:25 ` ttuttle
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=20120201211116.GA30758@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ttuttle@chromium.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;
as well as URLs for NNTP newsgroup(s).