On 04/10/17 22:27, Andrew Lunn wrote:
> Hi Richard
>
> It is generally unwanted.
>
> Have you tried back porting patches when the directory structure has
> changed? Files have moved around? It makes it a lot harder to
> do. Meaning patches are going to be back ported less often. Fixes
> which cou
On Wed, Oct 04, 2017 at 08:54:17PM +0200, Richard Siegfried wrote:
> On 04/10/17 01:03, David Miller wrote:
> > As someone who has to do backports regularly to -stable, there is no way
> > I am applying this.
> >
> > Sorry.
> Okay, I see.
>
> Is grouping files into subdirectories something genera
On 04/10/17 01:03, David Miller wrote:
> As someone who has to do backports regularly to -stable, there is no way
> I am applying this.
>
> Sorry.
Okay, I see.
Is grouping files into subdirectories something generally
unwanted/unlikely to be applied or is this specific to TCP / networking?
Becau
From: Richard Sailer
Date: Wed, 4 Oct 2017 00:22:10 +0200
> net/ipv4 currently contains around 100 source files containing the
> IP implementation and lots of other functionality (UDP, TCP, xfrm, etc.)
As someone who has to do backports regularly to -stable, there is no way
I am applying this.
On Wed, 2017-10-04 at 00:22 +0200, Richard Sailer wrote:
> net/ipv4 currently contains around 100 source files containing the
> IP implementation and lots of other functionality (UDP, TCP, xfrm, etc.)
>
> # 1/3
> To make the networking source tree more self documenting and well
> structured 1/3 m
net/ipv4 currently contains around 100 source files containing the
IP implementation and lots of other functionality (UDP, TCP, xfrm, etc.)
# 1/3
To make the networking source tree more self documenting and well
structured 1/3 moves the 30 shared TCP source files to a own
subdirectory of net/ipv
