From: Greg KH <gregkh@linuxfoundation.org>
To: ttuttle <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 14:02:32 -0800 [thread overview]
Message-ID: <20120201220232.GB893@kroah.com> (raw)
In-Reply-To: <CADyrwZSN6xeibZzgaPCL7qZfpwrTLipkXwQUOTOMZGpg0uRhHw@mail.gmail.com>
On Wed, Feb 01, 2012 at 04:47:22PM -0500, ttuttle wrote:
> On Wed, Feb 1, 2012 at 16:11, Greg KH <gregkh@linuxfoundation.org> wrote:
> >> + 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?
>
> This would happen if we found a device that was returning an
> unexpected USB configuration. We've never actually seen this happen
> -- it was just there in case. I can drop it if you think it's not
> worth the trouble.
As the code properly handles such an error, my point is, if a user sees
this new scary message, what are they supposed to do with it?
So yes, please drop it.
Are you going to resend this series based on the comments so far?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-02-01 22:06 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
[not found] ` <20120201211116.GA30758-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-02-01 21:47 ` ttuttle
2012-02-01 22:02 ` Greg KH [this message]
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=20120201220232.GB893@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 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.