From: Eric Dumazet <eric.dumazet@gmail.com>
To: Vito Caputo <vcaputo@pengaru.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] net: core: skbuff: skb_checksum_setup() drop err
Date: Sun, 13 Oct 2019 13:20:27 -0700 [thread overview]
Message-ID: <41da7b75-689f-9065-dec8-931ff9b4b91c@gmail.com> (raw)
In-Reply-To: <20191013201716.dwxfbr5kbueexomw@shells.gnugeneration.com>
On 10/13/19 1:17 PM, Vito Caputo wrote:
>
> Except there are examples under net/core of precisely this pattern, e.g.:
>
>
We do not care about having consistent code styles.
linux kernel has been contributed by thousands.
Each contributor has its own preferences.
We do not want to enforce very strong rules.
This is all cosmetic.
The real things we care are the backports we have to do every day.
Having these 'cleanups' in the way make our life miserable.
prev parent reply other threads:[~2019-10-13 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 0:30 [PATCH] net: core: skbuff: skb_checksum_setup() drop err Vito Caputo
2019-10-13 19:58 ` Eric Dumazet
2019-10-13 20:17 ` Vito Caputo
2019-10-13 20:20 ` Eric Dumazet [this message]
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=41da7b75-689f-9065-dec8-931ff9b4b91c@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vcaputo@pengaru.com \
/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