From: Greg KH <gregkh@linuxfoundation.org>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: stable@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 3.18.y] Fix compilation error backporting upstream commit 9fc12023d6f5
Date: Sat, 4 Aug 2018 14:40:34 +0200 [thread overview]
Message-ID: <20180804124034.GA4920@kroah.com> (raw)
In-Reply-To: <20180804122741.7178-1-lorenzo.bianconi@redhat.com>
On Sat, Aug 04, 2018 at 02:27:41PM +0200, Lorenzo Bianconi wrote:
> Fix following compilation error backporting upstream commit
> 9fc12023d6f5 ("ipv4: remove BUG_ON() from fib_compute_spec_dst)
>
> net/ipv4/fib_frontend.c: In function 'fib_compute_spec_dst':
> net/ipv4/fib_frontend.c:225:3: error: expected expression before 'if'
> if (!fib_lookup(net, &fl4, &res))
>
> net/ipv4/fib_frontend.c:200:20: warning: unused variable 'res'
> struct fib_result res;
>
> Fixes: 0e46da6c6fac ("ipv4: remove BUG_ON() from fib_compute_spec_dst")
> Signed-off-by: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
> ---
> net/ipv4/fib_frontend.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/ipv4/fib_frontend.c b/net/ipv4/fib_frontend.c
> index 924db4bedd88..0b29649627a7 100644
> --- a/net/ipv4/fib_frontend.c
> +++ b/net/ipv4/fib_frontend.c
> @@ -221,7 +221,7 @@ __be32 fib_compute_spec_dst(struct sk_buff *skb)
> fl4.saddr = 0;
> fl4.flowi4_tos = RT_TOS(ip_hdr(skb)->tos);
> fl4.flowi4_scope = scope;
> - fl4.flowi4_mark = vmark ? skb->mark : 0,
> + fl4.flowi4_mark = vmark ? skb->mark : 0;
> if (!fib_lookup(net, &fl4, &res))
> return FIB_RES_PREFSRC(net, res);
> } else {
Thanks, but I fixed this about 6 hours ago, right?
greg k-h
next prev parent reply other threads:[~2018-08-04 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 12:27 [PATCH 3.18.y] Fix compilation error backporting upstream commit 9fc12023d6f5 Lorenzo Bianconi
2018-08-04 12:40 ` Greg KH [this message]
2018-08-04 12:59 ` Lorenzo Bianconi
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=20180804124034.GA4920@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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).