From: Stefano Brivio <sbrivio@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: walteste@inf.ethz.ch, bcodding@redhat.com, gsierohu@redhat.com,
nforro@redhat.com, edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ipv4: Return -ENETUNREACH if we can't create route but saddr is valid
Date: Wed, 16 Oct 2019 20:51:38 +0200 [thread overview]
Message-ID: <20191016205138.0c5a0058@redhat.com> (raw)
In-Reply-To: <20191016.142159.1388461310782297107.davem@davemloft.net>
On Wed, 16 Oct 2019 14:21:59 -0400 (EDT)
David Miller <davem@davemloft.net> wrote:
> From: Stefano Brivio <sbrivio@redhat.com>
> Date: Thu, 10 Oct 2019 17:51:50 +0200
>
> > I think this should be considered for -stable, < 5.2
>
> Changes meant for -stable should not target net-next, but rather net.
Oh, sorry for that. I thought this would be the best way for patches
that are not strictly (or proven) fixes for net, but still make sense
for stable.
I generalised David Ahern's hint from a different case, I thought you
agreed (<20190618.092512.1610110055396742434.davem@davemloft.net>).
Resending for net now.
--
Stefano
prev parent reply other threads:[~2019-10-16 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 15:51 [PATCH net-next] ipv4: Return -ENETUNREACH if we can't create route but saddr is valid Stefano Brivio
2019-10-16 18:21 ` David Miller
2019-10-16 18:51 ` Stefano Brivio [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=20191016205138.0c5a0058@redhat.com \
--to=sbrivio@redhat.com \
--cc=bcodding@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gsierohu@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nforro@redhat.com \
--cc=walteste@inf.ethz.ch \
/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.