linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Santiago Ruano Rincón" <santiago.ruano-rincon@imt-atlantique.fr>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, Oliver Neukum <oneukum@suse.de>,
	miguel@det.uvigo.es, 965074@bugs.debian.org
Subject: Re: Patches to make multicast proccesing on CDC NCM drivers
Date: Thu, 3 Sep 2020 09:50:37 +0200	[thread overview]
Message-ID: <20200903075037.GD242939@bartik> (raw)
In-Reply-To: <20200902154517.GB2037986@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]

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:
> > El 02/09/20 a las 14:05, Greg KH escribió:
> > > On Wed, Sep 02, 2020 at 01:47:18PM +0200, Santiago Ruano Rincón wrote:
> > > > El 30/07/20 a las 16:07, Oliver Neukum escribió:
> > > > > Am Donnerstag, den 30.07.2020, 15:53 +0200 schrieb Santiago Ruano
> > > > > Rincón:
> > > > 
> > > > It would be possible to apply/backport Miguel's patches (along with
> > > > 5fd99b5d9950d6300467ded18ff4e44af0b4ae55) to stable versions please?
> > > 
> > > I don't see that git commit id in Linus's tree, are you sure it is
> > > correct?
> > 
> > I should had mention it is found in linux-next, sorry. Please see
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969365#10
> 
> Ah, nothing I can do with patches that are not yet in Linus's tree.
> 

ACK.

> > > > FWIW, in the context of Debian, I'm personally interested in 4.19.y.
> > > 
> > > What specific list of commits are you wanting to see backported?
> > 
> > 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 want to have them in linux stable releases because that would make
easier to include them in Debian stable release.

Thanks!

 -- Santiago

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2020-09-03  7:50 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 [this message]
     [not found]           ` <159483131513.13666.11657009071338024929.reportbug@kirby>
     [not found]             ` <20200903075037.GD242939__2852.23647240258$1599119665$gmane$org@bartik>
2020-09-03 17:17               ` Bug#965074: " Bjørn Mork

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=20200903075037.GD242939@bartik \
    --to=santiago.ruano-rincon@imt-atlantique.fr \
    --cc=965074@bugs.debian.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=miguel@det.uvigo.es \
    --cc=oneukum@suse.de \
    /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).