From: David Miller <davem@davemloft.net>
To: sbrivio@redhat.com
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 14:21:59 -0400 (EDT) [thread overview]
Message-ID: <20191016.142159.1388461310782297107.davem@davemloft.net> (raw)
In-Reply-To: <7bcfeaac2f78657db35ccf0e624745de41162129.1570722417.git.sbrivio@redhat.com>
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.
next prev parent reply other threads:[~2019-10-16 18:22 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 [this message]
2019-10-16 18:51 ` Stefano Brivio
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=20191016.142159.1388461310782297107.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bcodding@redhat.com \
--cc=edumazet@google.com \
--cc=gsierohu@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nforro@redhat.com \
--cc=sbrivio@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 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).