From: "Bjørn Mork" <bjorn@mork.no>
To: "Santiago Ruano Rincón" <santiago.ruano-rincon@imt-atlantique.fr>
Cc: Greg KH <gregkh@linuxfoundation.org>,
965074@bugs.debian.org, linux-usb@vger.kernel.org,
Oliver Neukum <oneukum@suse.de>,
miguel@det.uvigo.es
Subject: Re: Bug#965074: Patches to make multicast proccesing on CDC NCM drivers
Date: Thu, 03 Sep 2020 19:17:33 +0200 [thread overview]
Message-ID: <87o8mmn5jm.fsf@miraculix.mork.no> (raw)
In-Reply-To: <20200903075037.GD242939__2852.23647240258$1599119665$gmane$org@bartik> ("Santiago Ruano =?utf-8?Q?Rinc=C3=B3n=22's?= message of "Thu, 3 Sep 2020 09:50:37 +0200")
Santiago Ruano Rincón <santiago.ruano-rincon@imt-atlantique.fr> writes:
> El 02/09/20 a las 17:45, Greg KH escribió:
>> On Wed, Sep 02, 2020 at 03:27:28PM +0200, Santiago Ruano Rincón wrote:
>>
>> > This:
>> >
>> > 37a2ebdd9e597ae1a0270ac747883ea8f6f767b6
>> > e10dcb1b6ba714243ad5a35a11b91cc14103a9a9
>> > e506addeff844237d60545ef4f6141de21471caf
>> > 0226009ce0f6089f9b31211f7a2703cf9a327a01
>>
>> These do not look like bugfixes, but a new feature being added for this
>> driver. So why not just use a newer kernel version for this feature?
>
> From my point of view as user these are bugfixes, since IPv6 NDP or any
> other protocol relying on multicast do not work without them. In other
> words, my computer's networking is broken.
I was in doubt when I submitted these, but ended up specfying net-next
instead of net+stable as the target for a reason. This is a new feature
as Greg says. Even if the feature is essential for your use case, it is
still new. "Has never been supported" isn't really a bug.
And I am still convinced that my decision was correct. The patches are
a bit more intrusive than I'd be comfortable submitting to stable, as
was demonstrated by the stupid build bug I added... Fixed by commit
5fd99b5d9950 ("net: cdc_ncm: Fix build error") BTW.
> I want to have them in linux stable releases because that would make
> easier to include them in Debian stable release.
This has not been an absolute requirement in the past. Distros tend to
have a more relaxed stable policy.
Using a newer kernel until Debian moves on is obviously also an option.
Bjørn
prev parent reply other threads:[~2020-09-03 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 13:53 Patches to make multicast proccesing on CDC NCM drivers Santiago Ruano Rincón
2020-07-30 14:07 ` Oliver Neukum
2020-09-02 11:47 ` Santiago Ruano Rincón
2020-09-02 12:05 ` Greg KH
2020-09-02 13:27 ` Santiago Ruano Rincón
2020-09-02 15:45 ` Greg KH
2020-09-03 7:50 ` Santiago Ruano Rincón
[not found] ` <159483131513.13666.11657009071338024929.reportbug@kirby>
[not found] ` <20200903075037.GD242939__2852.23647240258$1599119665$gmane$org@bartik>
2020-09-03 17:17 ` Bjørn Mork [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=87o8mmn5jm.fsf@miraculix.mork.no \
--to=bjorn@mork.no \
--cc=965074@bugs.debian.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=miguel@det.uvigo.es \
--cc=oneukum@suse.de \
--cc=santiago.ruano-rincon@imt-atlantique.fr \
/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).