public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail•com>
To: Paolo Abeni <pabeni@redhat•com>, Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Paul Moore <paul@paul-moore•com>,
	"David S. Miller" <davem@davemloft•net>,
	netdev@vger•kernel.org
Subject: Re: linux-next: Tree for Jul 26
Date: Wed, 26 Jul 2017 19:48:56 +0900	[thread overview]
Message-ID: <20170726104856.GA5755@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20170726161203.1dfbcff9@canb.auug.org.au>

Hello,

On (07/26/17 16:12), Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20170725:
> 
> Non-merge commits (relative to Linus' tree): 2358
>  2466 files changed, 86994 insertions(+), 44655 deletions(-)


dce4551cb2adb1ac ("udp: preserve head state for IP_CMSG_PASSSEC")
causes a build error

net/ipv4/udp.c: In function ‘__udp_queue_rcv_skb’:
net/ipv4/udp.c:1789:49: error: ‘struct sk_buff’ has no member named ‘sp’; did you mean ‘sk’?
  if (likely(IPCB(skb)->opt.optlen == 0 && !skb->sp))
                                                 ^

	-ss

  reply	other threads:[~2017-07-26 10:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26  6:12 linux-next: Tree for Jul 26 Stephen Rothwell
2017-07-26 10:48 ` Sergey Senozhatsky [this message]
2017-07-26 13:09   ` Rosen, Rami
2017-07-26 13:18     ` Sergey Senozhatsky
  -- strict thread matches above, loose matches on Subject: below --
2024-07-26  3:06 Stephen Rothwell
2023-07-26  5:27 Stephen Rothwell
2022-07-26 11:49 Stephen Rothwell
2021-07-26 21:47 Mark Brown
2019-07-26  5:23 Stephen Rothwell
2018-07-26  9:42 Stephen Rothwell
2016-07-26  5:59 Stephen Rothwell
2013-07-26  7:22 Stephen Rothwell

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=20170726104856.GA5755@jagdpanzerIV.localdomain \
    --to=sergey.senozhatsky.work@gmail$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=paul@paul-moore$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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