From: Andrew Lunn <andrew@lunn.ch>
To: Richard Siegfried <richard_siegfried@systemli.org>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] A own subdirectory for shared TCP code
Date: Wed, 4 Oct 2017 22:27:49 +0200 [thread overview]
Message-ID: <20171004202749.GB13247@lunn.ch> (raw)
In-Reply-To: <d7237d11-ec83-0ef6-d201-da8b99c94b88@systemli.org>
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 generally
> unwanted/unlikely to be applied or is this specific to TCP / networking?
>
> Because there are several other places in the source tree where I would
> like to group things.
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 could be security relevant might not get back ported, etc.
Kernel 4.4 is going to be supported until 2022. So moving files around
is going to make Greg Kroah-Hartman life more difficult for the next 5
years.
Andrew
next prev parent reply other threads:[~2017-10-04 20:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 22:22 [PATCH net-next 0/3] A own subdirectory for shared TCP code Richard Sailer
2017-10-03 22:22 ` [PATCH net-next 1/3] net/ipv4: Move shared tcp code to own subdirectory Richard Sailer
2017-10-03 22:22 ` [PATCH net-next 2/3] tcp: Move cc algorithms " Richard Sailer
2017-10-03 22:22 ` [PATCH net-next 3/3] Move shared tcp code to net/ipv4v6shared Richard Sailer
[not found] ` <CAOaVG14r2Uwm+r17Oa9jwKj50vRr8=SqwXEmmGAeW8rHj3FgXg@mail.gmail.com>
2017-10-04 8:57 ` Richard Siegfried
2017-10-03 22:42 ` [PATCH net-next 0/3] A own subdirectory for shared TCP code Eric Dumazet
2017-10-03 23:03 ` David Miller
2017-10-04 18:54 ` Richard Siegfried
2017-10-04 20:27 ` Andrew Lunn [this message]
2017-10-05 13:17 ` Richard Siegfried
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=20171004202749.GB13247@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=richard_siegfried@systemli.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.