All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vignesh R <vigneshr@ti.com>
To: David Miller <davem@davemloft.net>
Cc: "oneukum@suse.com" <oneukum@suse.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"bjorn@mork.no" <bjorn@mork.no>
Subject: Re: [v2] cdc-ether: divorce initialisation with a filter reset and a generic method
Date: Wed, 4 Oct 2017 10:32:42 +0530	[thread overview]
Message-ID: <45d5058f-9108-8be6-bc2d-98f368bc0f66@ti.com> (raw)
In-Reply-To: <20171003.095955.1603961040065728073.davem@davemloft.net>



On Tuesday 03 October 2017 10:29 PM, David Miller wrote:
> From: Vignesh R <vigneshr@ti.com>
> Date: Tue, 3 Oct 2017 13:39:18 +0530
> 
>> Hi Dave,
>>
>> On Monday 22 May 2017 06:20 PM, Oliver Neukum wrote:
>>> Some devices need their multicast filter reset but others are crashed by that.
>>> So the methods need to be separated.
>>>
>>> Signed-off-by: Oliver Neukum <oneukum@suse.com>
>>> Reported-by: "Ridgway, Keith" <kridgway@harris.com>
>>> ---
>>
>> I see this patch was merged and said to be queued for -stable, but I
>> don't see this fix in any of the stable kernels. Would you please ask
>> for this patch to be backported to -stable kernels?
> 
> I submit networking -stable patches at a time of my own choosing.
> Usually 1 to 2 weeks after it gets applied to my tree.
> 

Sorry, but this patch was merged in v4.12-rc3(end of May) and I did not
see them in netdev stable patchwork nor in Greg's queue. Hence, I
thought this patch might have slipped through the cracks.

> Please be patient.
> 

-- 
Regards
Vignesh

  reply	other threads:[~2017-10-04  5:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 12:50 [PATCH v2] cdc-ether: divorce initialisation with a filter reset and a generic method Oliver Neukum
2017-05-23 15:01 ` David Miller
2017-10-03  8:09 ` [v2] " Vignesh R
2017-10-03 16:59   ` David Miller
2017-10-04  5:02     ` Vignesh R [this message]
2017-10-27  7:54       ` Vignesh R

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=45d5058f-9108-8be6-bc2d-98f368bc0f66@ti.com \
    --to=vigneshr@ti.com \
    --cc=bjorn@mork.no \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.com \
    /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.