From: Johan Hovold <johan@kernel.org>
To: Joel Stanley <joel@jms.id.au>
Cc: Eddie James <eajames@linux.ibm.com>,
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: Thu, 3 Mar 2022 11:13:48 +0100 [thread overview]
Message-ID: <YiCU3KI9Dh2psRnK@hovoldconsulting.com> (raw)
In-Reply-To: <CACPK8Xc9MnM9_jr7NrNLtqBrN_t8D7G-scQvk51vbpOU6LWeuw@mail.gmail.com>
On Thu, Mar 03, 2022 at 09:46:05AM +0000, Joel Stanley wrote:
> On Thu, 3 Mar 2022 at 09:44, Johan Hovold <johan@kernel.org> wrote:
> >
> > On Thu, Mar 03, 2022 at 09:24:51AM +0000, Joel Stanley wrote:
> > > On Thu, 3 Mar 2022 at 09:15, Johan Hovold <johan@kernel.org> wrote:
> > > >
> > > > On Thu, Mar 03, 2022 at 08:52:29AM +0000, Joel Stanley wrote:
> > > > > On Thu, 3 Mar 2022 at 08:25, Johan Hovold <johan@kernel.org> wrote:
> > > > > >
> > > > > > On Tue, Mar 01, 2022 at 04:44:46PM -0600, Eddie James wrote:
> > > > > > > IBM manufactures a PL2303 device for UPS communications. Add the vendor
> > > > > > > and product IDs so that the PL2303 driver binds to the device.
> > > > > > >
> > > > > > > Signed-off-by: Joel Stanley <joel@jms.id.au>
> > > > > > > Signed-off-by: Eddie James <eajames@linux.ibm.com>
> > > > > > > ---
> > > > > > > Changes since v1:
> > > > > > > - Fix commit message Signed-off-by ordering.
> > > > > >
> > > > > > Almost there. You're still missing a Co-developed-by tag, a From line,
> > > > > > or both.
> > > > >
> > > > > It's neither. This patch was applied to a tree by myself, and I asked
> > > > > Eddie to send it to mainline for merging.
> > > >
> > > > Then you are missing a From line. As the patch looks like know, Eddie is
> > > > considered the author and not you.
> > >
> > > You are incorrect. Eddie is the author.
> >
> > Then what is your SoB doing there in the first place? If Eddie is the
> > sole author as well as the submitter, and you didn't touch the patch in
> > between, then your SoB does not belong in the chain.
> >
> > If you applied Eddie's patch to your shared tree and Eddie generated a
> > patch from there, then the chain should be:
> >
> > SoB: E
> > SoB: J
> > SoB: E
> >
> > but this is starting to look a bit ridiculous.
>
> I agree. I would appreciate it if you applied the patch, with or
> without my sob in whatever order you deem fit.
Ok, I'll assume what you intended was E-J-E but that perhaps
git-format-patch swallowed the last SoB. Thanks for clarifying.
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?
Johan
next prev parent reply other threads:[~2022-03-03 10:13 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 [this message]
2022-03-03 21:48 ` Eddie James
2022-03-04 8:48 ` Johan Hovold
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=YiCU3KI9Dh2psRnK@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 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.