public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Oliver Neukum <oneukum@suse.com>
Cc: bids.7405@bigpond.com, linux-usb@vger.kernel.org,
	netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH] USB: zaurus: support another broken Zaurus
Date: Thu, 10 Feb 2022 15:17:47 +0100	[thread overview]
Message-ID: <YgUei+MqkHAE2Oet@kroah.com> (raw)
In-Reply-To: <6d5a8cb4-1823-cecb-a31e-2118a95c96a6@suse.com>

On Thu, Feb 10, 2022 at 03:13:49PM +0100, Oliver Neukum wrote:
> 
> On 10.02.22 13:58, Greg KH wrote:
> > On Thu, Feb 10, 2022 at 01:26:43PM +0100, Oliver Neukum wrote:
> >> This SL-6000 says Direct Line, not Ethernet
> >>
> >> Signed-off-by: Oliver Neukum <oneukum@suse.com>
> >> ---
> >>  drivers/net/usb/cdc_ether.c | 12 ++++++++++++
> >>  drivers/net/usb/zaurus.c    | 12 ++++++++++++
> >>  2 files changed, 24 insertions(+)
> >>
> >> diff --git a/drivers/net/usb/cdc_ether.c b/drivers/net/usb/cdc_ether.c
> >> index eb3817d70f2b..9b4dfa3001d6 100644
> >> --- a/drivers/net/usb/cdc_ether.c
> >> +++ b/drivers/net/usb/cdc_ether.c
> >> @@ -583,6 +583,11 @@ static const struct usb_device_id	products[] = {
> >>  	.bInterfaceSubClass	= USB_CDC_SUBCLASS_ETHERNET, \
> >>  	.bInterfaceProtocol	= USB_CDC_PROTO_NONE
> >>  
> >> +#define ZAURUS_FAKE_INTERFACE \
> >> +	.bInterfaceClass	= USB_CLASS_COMM, \
> >> +	.bInterfaceSubClass	= USB_CDC_SUBCLASS_MDLM, \
> >> +	.bInterfaceProtocol	= USB_CDC_PROTO_NONE
> >> +
> >>  /* SA-1100 based Sharp Zaurus ("collie"), or compatible;
> >>   * wire-incompatible with true CDC Ethernet implementations.
> >>   * (And, it seems, needlessly so...)
> >> @@ -636,6 +641,13 @@ static const struct usb_device_id	products[] = {
> >>  	.idProduct              = 0x9032,	/* SL-6000 */
> >>  	ZAURUS_MASTER_INTERFACE,
> >>  	.driver_info		= 0,
> >> +}, {
> >> +	.match_flags    =   USB_DEVICE_ID_MATCH_INT_INFO
> >> +		 | USB_DEVICE_ID_MATCH_DEVICE,
> >> +	.idVendor               = 0x04DD,
> >> +	.idProduct              = 0x9032,	/* SL-6000 */
> >> +	ZAURUS_FAKE_INTERFACE,
> >> +	.driver_info		= 0,
> >>  }, {
> >>  	.match_flags    =   USB_DEVICE_ID_MATCH_INT_INFO
> >>  		 | USB_DEVICE_ID_MATCH_DEVICE,
> >> diff --git a/drivers/net/usb/zaurus.c b/drivers/net/usb/zaurus.c
> >> index 8e717a0b559b..9243be9bd2aa 100644
> >> --- a/drivers/net/usb/zaurus.c
> >> +++ b/drivers/net/usb/zaurus.c
> >> @@ -256,6 +256,11 @@ static const struct usb_device_id	products [] = {
> >>  	.bInterfaceSubClass	= USB_CDC_SUBCLASS_ETHERNET, \
> >>  	.bInterfaceProtocol	= USB_CDC_PROTO_NONE
> >>  
> >> +#define ZAURUS_FAKE_INTERFACE \
> >> +	.bInterfaceClass	= USB_CLASS_COMM, \
> >> +	.bInterfaceSubClass	= USB_CDC_SUBCLASS_MDLM, \
> >> +	.bInterfaceProtocol	= USB_CDC_PROTO_NONE
> >> +
> >>  /* SA-1100 based Sharp Zaurus ("collie"), or compatible. */
> >>  {
> >>  	.match_flags	=   USB_DEVICE_ID_MATCH_INT_INFO
> >> @@ -313,6 +318,13 @@ static const struct usb_device_id	products [] = {
> >>  	.idProduct              = 0x9032,	/* SL-6000 */
> >>  	ZAURUS_MASTER_INTERFACE,
> >>  	.driver_info = ZAURUS_PXA_INFO,
> >> +}, {
> >> +        .match_flags    =   USB_DEVICE_ID_MATCH_INT_INFO
> >> +                 | USB_DEVICE_ID_MATCH_DEVICE,
> >> +        .idVendor               = 0x04DD,
> >> +        .idProduct              = 0x9032,       /* SL-6000 */
> >> +        ZAURUS_FAKE_INTERFACE,
> >> +        .driver_info = (unsigned long) &bogus_mdlm_info,
> > No tabs here?
> Checking ...
> >
> > And isn't there a needed "Reported-by:" for this one as it came from a
> > bug report?
> Do we do these for reports by the kernel.org bugzilla?

We should, why not?


  reply	other threads:[~2022-02-10 14:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 12:26 [PATCH] USB: zaurus: support another broken Zaurus Oliver Neukum
2022-02-10 12:58 ` Greg KH
2022-02-10 14:13   ` Oliver Neukum
2022-02-10 14:17     ` Greg KH [this message]
2022-02-10 14:20       ` Oliver Neukum
2022-02-10 14:49         ` Greg KH

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=YgUei+MqkHAE2Oet@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bids.7405@bigpond.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.com \
    /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