From: Jakub Kicinski <kuba@kernel.org>
To: Tree Davies <tdavies@darkphysics.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
edumazet@google.com, intel-wired-lan@lists.osuosl.org,
anthony.l.nguyen@intel.com, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH] net/e1000: Fix single statement blocks warning
Date: Mon, 12 Jun 2023 15:05:26 -0700 [thread overview]
Message-ID: <20230612150526.10ca14ac@kernel.org> (raw)
In-Reply-To: <ZIZI5czU2Qv5KrPA@oatmeal.darkphysics>
On Sun, 11 Jun 2023 15:21:36 -0700 Tree Davies wrote:
> This patch fixes checkpatch.pl warning of type:
> WARNING: braces {} are not necessary for single statement blocks
We don't accept pure checkpatch "fixes" in networking, sorry.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Tree Davies <tdavies@darkphysics.net>
Cc: anthony.l.nguyen@intel.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/e1000: Fix single statement blocks warning
Date: Mon, 12 Jun 2023 15:05:26 -0700 [thread overview]
Message-ID: <20230612150526.10ca14ac@kernel.org> (raw)
In-Reply-To: <ZIZI5czU2Qv5KrPA@oatmeal.darkphysics>
On Sun, 11 Jun 2023 15:21:36 -0700 Tree Davies wrote:
> This patch fixes checkpatch.pl warning of type:
> WARNING: braces {} are not necessary for single statement blocks
We don't accept pure checkpatch "fixes" in networking, sorry.
next prev parent reply other threads:[~2023-06-12 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 22:21 [Intel-wired-lan] [PATCH] net/e1000: Fix single statement blocks warning Tree Davies
2023-06-11 22:21 ` Tree Davies
2023-06-12 22:05 ` Jakub Kicinski [this message]
2023-06-12 22:05 ` Jakub Kicinski
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=20230612150526.10ca14ac@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tdavies@darkphysics.net \
/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.