All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kumlien <ian.kumlien@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: Saeed Mahameed <saeedm@mellanox.com>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [ISSUE][4.20.6] mlx5 and checksum failures
Date: Wed, 6 Feb 2019 23:12:53 +0100	[thread overview]
Message-ID: <CAA85sZt0=a2DDBp0fbVH15DC+=+Q+Rb7ig_09xpNM3smDAT-ZA@mail.gmail.com> (raw)
In-Reply-To: <20190206.140314.1579572356051091256.davem@davemloft.net>

On Wed, Feb 6, 2019 at 11:03 PM David Miller <davem@davemloft.net> wrote:
> From: Saeed Mahameed <saeedm@mellanox.com>
> Date: Wed, 6 Feb 2019 17:18:55 +0000

> > On Wed, 2019-02-06 at 17:16 +0100, Ian Kumlien wrote:
> >> Hi,
> >>
> >> I'm hitting an issue that i think is fixed by the following patch,
> >> i haven't verified it yet - but it looks like it should go on the
> >> stable queue(?)
> >>
> >> (And yes, I did look, and couldn't find it ;))
> >>
> >
> > Yes, i couldn't find it neither,
> >
> > It should have been queued up for 4.18 by now.
> > Dave said he will take care of it, maybe he just forgot or something.
> > since the patch needed some extra care..
> >
> > https://patchwork.ozlabs.org/patch/1027837/
> >
> > Dave, Is there anything i can do here ?
>
> I never handle anything past the most recent two -stable releases,
> which right now is 4.20 and 4.19

Could we please schedule this for 4.19 and 4.20 - it's kinda breaking things

> For anything beyond that you have to contact the person who maintains
> that -stable tree.

I think it needs to be applied to all -stable since 4.18 :/

  reply	other threads:[~2019-02-06 22:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 16:16 [ISSUE][4.20.6] mlx5 and checksum failures Ian Kumlien
2019-02-06 17:18 ` Saeed Mahameed
2019-02-06 22:03   ` David Miller
2019-02-06 22:12     ` Ian Kumlien [this message]
2019-02-06 22:22       ` David Miller
2019-02-06 22:33         ` Ian Kumlien
2019-02-06 22:38       ` Cong Wang
2019-02-06 22:41         ` Ian Kumlien
2019-02-06 22:49           ` Cong Wang
2019-02-06 23:00             ` Ian Kumlien
2019-02-07  1:00               ` Saeed Mahameed
2019-02-07 10:16                 ` Ian Kumlien
2019-02-07 18:42                   ` Saeed Mahameed
2019-02-07 22:01                     ` Ian Kumlien
2019-02-08 16:29                       ` Ian Kumlien
2019-02-09 15:54                         ` Ian Kumlien
2019-02-13 12:04                           ` Ian Kumlien
2019-02-13 23:36                             ` Saeed Mahameed
2019-02-07 21:40           ` Marcelo Ricardo Leitner

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='CAA85sZt0=a2DDBp0fbVH15DC+=+Q+Rb7ig_09xpNM3smDAT-ZA@mail.gmail.com' \
    --to=ian.kumlien@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@mellanox.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.