linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Eddie James <eajames@linux.ibm.com>
Cc: Joel Stanley <joel@jms.id.au>,
	linux-usb@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2] USB: serial: pl2303: Add IBM device IDs
Date: Fri, 4 Mar 2022 09:48:43 +0100	[thread overview]
Message-ID: <YiHSa6bCmDTdS3dU@hovoldconsulting.com> (raw)
In-Reply-To: <b1ec9ab3-d621-fa66-0fae-f966242f3f7f@linux.ibm.com>

On Thu, Mar 03, 2022 at 03:48:37PM -0600, Eddie James wrote:
> On 3/3/22 04:13, Johan Hovold wrote:

> > I was going to apply to the patch, but I see now that you didn't provide
> > any details about the product apart from it being a UPS and that's not
> > reflected in the define name.
> >
> > Do you have a pointer to device (family) in question?

> It's a pretty generic pl2303 device and doesn't have to be used for UPS, 
> but that is our use-case. Here is a page with some detail about the 
> device: 
> https://www.ibm.com/docs/en/power9/9009-22A?topic=power-uninterruptible-supply

Ah, ok, I thought it may have been built into the UPS.

I've applied the patch now, thanks!

Johan

  reply	other threads:[~2022-03-04  8:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 22:44 [PATCH v2] USB: serial: pl2303: Add IBM device IDs Eddie James
2022-03-03  8:25 ` Johan Hovold
2022-03-03  8:52   ` Joel Stanley
2022-03-03  9:15     ` Johan Hovold
2022-03-03  9:24       ` Joel Stanley
2022-03-03  9:44         ` Johan Hovold
2022-03-03  9:46           ` Joel Stanley
2022-03-03 10:13             ` Johan Hovold
2022-03-03 21:48               ` Eddie James
2022-03-04  8:48                 ` Johan Hovold [this message]
2022-03-11  9:37                 ` 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=YiHSa6bCmDTdS3dU@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=eajames@linux.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joel@jms.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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).