All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Giacinto Cifelli <gciofono@gmail.com>
Cc: Johan Hovold <johan@kernel.org>,
	linux-usb@vger.kernel.org, Lars Melin <larsm17@gmail.com>
Subject: Re: [PATCH] option: added support for Thales Cinterion EXS82 option port.
Date: Wed, 25 Nov 2020 11:08:34 +0100	[thread overview]
Message-ID: <X74tIqR+UOH/E4Sz@localhost> (raw)
In-Reply-To: <CAKSBH7Gha4rwacF-gE26x9pTsAgeV3ASvb+BYm5Xz_B3jN_BqQ@mail.gmail.com>

On Wed, Nov 25, 2020 at 11:00:26AM +0100, Giacinto Cifelli wrote:
> Hi Johan,
> 
> On Wed, Nov 25, 2020 at 10:40 AM Johan Hovold <johan@kernel.org> wrote:
> >
> > On Tue, Nov 24, 2020 at 10:41:55AM +0100, Giacinto Cifelli wrote:
> > > There is a single option port in this modem, and it is used as debug port
> > >
> > > Signed-off-by: Giacinto Cifelli <gciofono@gmail.com>
> >
> > Thanks for the update (and thanks for the review, Lars).
> >
> > Using the option driver for just a debug port seems like overkill, but
> > ok.
> >
> > Some form issues:
> >
> >  - When updating a patch always include a patch revision number in the
> >    Subject prefix (e.g. "[PATCH v2] USB: serial: option: add ...").
> >
> 
> technically this is a new patch, as I have changed the name, but I was
> reserving the v2 for the actual MV31 patch that I will send in the
> near future.

Since it's the same PID you're adding I'd still consider this a v2 even
if you changed the product name, but I see your point.

> >  - Try to follow the convention used by the subsystem for the Subject
> >    prefix (i.e. "USB: serial: option: add ...").
> 
> ok. Should I re-submit this patch?  Do you prefer v2 or v3 for a new submit?

Yes, please do send a v3.

Johan

      reply	other threads:[~2020-11-25 10:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24  9:41 [PATCH] option: added support for Thales Cinterion EXS82 option port Giacinto Cifelli
2020-11-25  9:40 ` Johan Hovold
2020-11-25 10:00   ` Giacinto Cifelli
2020-11-25 10:08     ` Johan Hovold [this message]

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=X74tIqR+UOH/E4Sz@localhost \
    --to=johan@kernel.org \
    --cc=gciofono@gmail.com \
    --cc=larsm17@gmail.com \
    --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.