linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Johan Hovold <johan@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Subject: Re: [PATCH 2/2] visor: Match I330 phone more precisely
Date: Wed, 29 Apr 2015 12:43:22 +0200	[thread overview]
Message-ID: <20150429104322.GB32318@localhost> (raw)
In-Reply-To: <20150422143012.GC16828@localhost>

On Wed, Apr 22, 2015 at 04:30:12PM +0200, Johan Hovold wrote:
> On Wed, Apr 22, 2015 at 02:35:09PM +0200, Jason A. Donenfeld wrote:
> > Samsung has just released a portable USB3 SSD, coming in a very small
> > and nice form factor. It's USB ID is 04e8:8001, which unfortunately is
> > already used by the Palm Visor driver for the Samsung I330 phone cradle.
> > Having pl2303 or visor pick up this device ID results in conflicts with
> > the usb-storage driver, which handles the newly released portable USB3
> > SSD.
> > 
> > To work around this conflict, I've dug up a mailing list post [1] from a
> > long time ago, in which a user posts the full USB descriptor
> > information. The most specific value in this appears to be the interface
> > class, which has value 255 (0xff). Since usb-storage requires an
> > interface class of 0x8, I believe it's correct to disambiguate the two
> > devices by matching on 0xff inside visor.
> > 
> > [1] http://permalink.gmane.org/gmane.linux.usb.user/4264
> > 
> > Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> 
> Both patches look good, but next time remember to include a patch
> revision in the subject of all patches in a series (this would be
> [PATCH v3]). Please use a "USB: " prefix as well.
> 
> I'll fix it up before applying this time.

Both patches now applied with stable tags.

Thanks,
Johan

  reply	other threads:[~2015-04-29 10:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 15:07 [PATCH] pl2303: Remove antiquated support for I330 phone Jason A. Donenfeld
2015-04-21 17:03 ` Greg Kroah-Hartman
2015-04-22 10:14   ` [PATCH] pl2303, visor: Match I330 phone more precisely Jason A. Donenfeld
2015-04-22 10:28     ` Sergei Shtylyov
2015-04-22 11:20     ` Johan Hovold
2015-04-22 12:35       ` [PATCH 1/2] pl2303: Remove support for Samsung I330 Jason A. Donenfeld
2015-04-22 12:35         ` [PATCH 2/2] visor: Match I330 phone more precisely Jason A. Donenfeld
2015-04-22 14:30           ` Johan Hovold
2015-04-29 10:43             ` Johan Hovold [this message]
2015-04-22 12:38       ` [PATCH] pl2303, " Greg Kroah-Hartman
2015-04-22 12:42         ` Jason A. Donenfeld
2015-04-22 13:33           ` Greg Kroah-Hartman
2015-04-22 12:48         ` [PATCH 1/2] visor: Remove support for Samsung I330 Jason A. Donenfeld
2015-04-22 12:48           ` [PATCH 2/2] pl2303: Match I330 phone more precisely Jason A. Donenfeld
2015-04-22 14:20         ` [PATCH] pl2303, visor: " Johan Hovold
2015-04-22 14:58           ` Greg Kroah-Hartman
2015-04-22 15:02             ` Johan Hovold

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=20150429104322.GB32318@localhost \
    --to=johan@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).