From: Davide Tronchin <davide.tronchin.94@gmail.com>
To: johan@kernel.org
Cc: cesare.marzano@gmail.com, davide.tronchin.94@gmail.com,
gregkh@linuxfoundation.org, larsm17@gmail.com,
linux-usb@vger.kernel.org, marco.demarco@posteo.net
Subject: Re: [PATCH v5 1/3] USB: serial: option: remove old LARA-R6 PID
Date: Tue, 15 Nov 2022 17:46:54 +0100 [thread overview]
Message-ID: <20221115164654.38632-1-davide.tronchin.94@gmail.com> (raw)
In-Reply-To: <Y3NmKk0Xte04qxwS@hovoldconsulting.com>
My apologies, this is my first attempt to submit a patch to the kernel
community.
> We've asked you repeatedly whether you for u-blox or not, but you keep
> ignoring this question. Knowing this would allow us to better evaluate
> the reasoning and motivation behind this this change.
Yes, i am a u-blox employee and i've been asked to integrate LARA-L6 in
the linux kernel and update the current code for LARA-R6 00B (updating
the PID from 0x90fa to 0x908b).
> The above commit message still does not explain why you want to remove
> it and whether it would be safe to do so. Why was added in the first
> place? What u-blox products used the old PID?
The first prototype of LARA-R6 00B had 0x90fa PID but, just before the
product finalization, it has been decided to adopt a new USB composition
and consequently a change of PID was necessary.
The 0x90fa PID has been used only for some internal prototypes, hence
no u-blox products with that PID have been shipped to customers.
As pointed out in the discussion, the 0x90fa PID is used by other module
vendors which sell Qualcomm based modems, hence i proposed to remove the
association between u-blox (thedefine UBLOX_PRODUCT_R6XX) and 0x90fa,
moving it directly in the option_ids array.
> By just removing the define this is less of an issue, but you should
> not make the life of reviewers harder by ignoring request to properly
> motivate your changes and explain why they are safe to apply.
My apologies again, thanks for the patience.
> You can either put a shared changelog for the whole series in a cover
> letter, or you describe changes to each individual patch. But mixing the
> two styles as you do in this entry is just confusing.
Thanks for the suggestions. In order to simplify the submission process,
i propose to split the submission for the LARA-L6 patches and the update
for LARA-R6 00B.
Do you think could it be feasible?
Davide
next prev parent reply other threads:[~2022-11-15 16:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 9:27 [PATCH v3] USB: serial: option: the patch is meant to support LARA-R6 Cat 1 and LARA-L6 CAT 4 module family Davide Tronchin
2022-10-27 14:11 ` Johan Hovold
2022-11-08 16:29 ` [PATCH v4 1/3] USB: serial: option: remove old LARA-R6 PID Davide Tronchin
2022-11-08 16:30 ` [PATCH v4 2/3] USB: serial: option: add u-blox LARA-R6 00B modem Davide Tronchin
2022-11-08 16:30 ` [PATCH v4 3/3] USB: serial: option: add u-blox LARA-L6 modem Davide Tronchin
2022-11-09 4:10 ` Lars Melin
2022-11-15 10:18 ` Johan Hovold
2022-11-15 10:22 ` Johan Hovold
2022-11-15 16:50 ` Davide Tronchin
2022-11-16 8:10 ` Johan Hovold
2022-11-09 4:15 ` [PATCH v4 1/3] USB: serial: option: remove old LARA-R6 PID Lars Melin
2022-11-09 9:34 ` Lars Melin
2022-11-09 16:17 ` [PATCH v5 " Davide Tronchin
2022-11-09 16:17 ` [PATCH v5 2/3] USB: serial: option: add u-blox LARA-R6 00B modem Davide Tronchin
2022-11-09 16:17 ` [PATCH v5 3/3] USB: serial: option: add u-blox LARA-L6 modem Davide Tronchin
2022-11-15 10:12 ` [PATCH v5 1/3] USB: serial: option: remove old LARA-R6 PID Johan Hovold
2022-11-15 16:46 ` Davide Tronchin [this message]
2022-11-16 8:05 ` Johan Hovold
2022-11-16 9:50 ` Davide Tronchin
2022-11-16 9:55 ` Johan Hovold
2022-11-16 15:59 ` [PATCH v6 " Davide Tronchin
2022-11-16 15:59 ` [PATCH v6 2/3] USB: serial: option: add u-blox LARA-R6 00B modem Davide Tronchin
2022-11-16 15:59 ` [PATCH v6 3/3] USB: serial: option: add u-blox LARA-L6 modem Davide Tronchin
2022-11-16 16:28 ` 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=20221115164654.38632-1-davide.tronchin.94@gmail.com \
--to=davide.tronchin.94@gmail.com \
--cc=cesare.marzano@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=larsm17@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=marco.demarco@posteo.net \
/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).