Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 26 Aug 2020 17:49:15 +0300
From:   "David K. Kahurani" <k.kahurani@gmail.com>
To:     gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Cc:     admin@rapidseedbox.com, gichini.ngaruiya@gmail.com
Subject: Re: [PATCH 5.7 00/15] 5.7.19-rc1 review
Message-ID: <20200826144915.GD16589@metal>
References: <20200826114849.295321031@linuxfoundation.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200826114849.295321031@linuxfoundation.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Aug 26, 2020 at 02:02:28PM +0200, Greg Kroah-Hartman wrote:
> -------------------
> Note, ok, this is really going to be the final 5.7.y kernel release.  I
> mean it this time....
> -------------------

Hello,

This is probably not very relevant but let me just bring this up here since your manner of posting mail on the list seems to differ quite a bit from what most people on the list are doing.

From my understanding, an email regarding to a certain patch or kernel issue should be sent to a list and not to a maintainer. This is however not the habit that people are in, though but instead, most people will send the email to the maintainers, then cc a few probably random mailing lists. This leads to emails flooding on the mailing list and consequently, beats the purpose of one ever having sent the mail to a list because lists will get increasingly difficult to follow.

Is it just me who has made this observation? From your mail, it clearly looks and seems like you are following the above. Not following the above could make it very hard for a new kernel developer to pick up working on the kernel.

Sincerely,
David Kiarie

> 
> This is the start of the stable review cycle for the 5.7.19 release.
> There are 15 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Fri, 28 Aug 2020 11:48:35 +0000.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.19-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.7.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 
> -------------
> Pseudo-Shortlog of commits:
> 
> Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>     Linux 5.7.19-rc1
> 
> Max Filippov <jcmvbkbc@gmail.com>
>     binfmt_flat: revert "binfmt_flat: don't offset the data start"
> 
> Michael Ellerman <mpe@ellerman.id.au>
>     powerpc/64s: Don't init FSCR_DSCR in __init_FSCR()
> 
> Maxim Mikityanskiy <maximmi@mellanox.com>
>     ethtool: Don't omit the netlink reply if no features were changed
> 
> Maxim Mikityanskiy <maximmi@mellanox.com>
>     ethtool: Account for hw_features in netlink interface
> 
> Maxim Mikityanskiy <maximmi@mellanox.com>
>     ethtool: Fix preserving of wanted feature bits in netlink interface
> 
> Shay Agroskin <shayagr@amazon.com>
>     net: ena: Make missed_tx stat incremental
> 
> Cong Wang <xiyou.wangcong@gmail.com>
>     tipc: fix uninit skb->data in tipc_nl_compat_dumpit()
> 
> Xin Long <lucien.xin@gmail.com>
>     tipc: call rcu_read_lock() in tipc_aead_encrypt_done()
> 
> Peilin Ye <yepeilin.cs@gmail.com>
>     net/smc: Prevent kernel-infoleak in __smc_diag_dump()
> 
> David Laight <David.Laight@ACULAB.COM>
>     net: sctp: Fix negotiation of the number of data streams.
> 
> Alaa Hleihel <alaa@mellanox.com>
>     net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow
> 
> Necip Fazil Yildiran <necip@google.com>
>     net: qrtr: fix usage of idr in port assignment to socket
> 
> Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
>     net: nexthop: don't allow empty NHA_GROUP
> 
> Miaohe Lin <linmiaohe@huawei.com>
>     net: Fix potential wrong skb->protocol in skb_vlan_untag()
> 
> Mark Tomlinson <mark.tomlinson@alliedtelesis.co.nz>
>     gre6: Fix reception with IP6_TNL_F_RCV_DSCP_COPY
> 
> 
> -------------
> 
> Diffstat:
> 
>  Makefile                                     |  4 ++--
>  arch/powerpc/kernel/cpu_setup_power.S        |  2 +-
>  drivers/net/ethernet/amazon/ena/ena_netdev.c |  5 ++++-
>  fs/binfmt_flat.c                             | 20 ++++++++++++--------
>  net/core/skbuff.c                            |  4 ++--
>  net/ethtool/features.c                       | 19 ++++++++++---------
>  net/ipv4/nexthop.c                           |  5 ++++-
>  net/ipv6/ip6_tunnel.c                        | 10 +++++++++-
>  net/qrtr/qrtr.c                              | 20 +++++++++++---------
>  net/sched/act_ct.c                           |  2 +-
>  net/sctp/stream.c                            |  6 ++++--
>  net/smc/smc_diag.c                           | 16 +++++++++-------
>  net/tipc/crypto.c                            |  2 ++
>  net/tipc/netlink_compat.c                    | 12 +++++++++++-
>  14 files changed, 82 insertions(+), 45 deletions(-)
> 
>