The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: joaomboni <joaoboni017@gmail.com>
Cc: <anthony.l.nguyen@intel.com>, <andrew+netdev@lunn.ch>,
	<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
	<pabeni@redhat.com>, <intel-wired-lan@lists.osuosl.org>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] e1000: The 'const' qualifier has been added where applicable to enhance code safety and prevent unintended modifications.
Date: Tue, 4 Mar 2025 09:27:37 +0100	[thread overview]
Message-ID: <a17f8193-10cc-4e23-b2d1-125a336c9ce0@intel.com> (raw)
In-Reply-To: <20250303204751.145171-1-joaoboni017@gmail.com>

On 3/3/25 21:47, joaomboni wrote:
> Signed-off-by: Joao Bonifacio <joaoboni017@gmail.com>

it will be good to use imperative mood in the Subject,
and add one more paragraph, like:

Subject: e1000: mark global variables const where possible

Next paragraph:
Mark global variables const, so unintended modification would not be
possible.

> ---
>   drivers/net/ethernet/intel/e1000/e1000_main.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ethernet/intel/e1000/e1000_main.c b/drivers/net/ethernet/intel/e1000/e1000_main.c
> index 3f089c3d47b2..96bc85f09aaf 100644
> --- a/drivers/net/ethernet/intel/e1000/e1000_main.c
> +++ b/drivers/net/ethernet/intel/e1000/e1000_main.c
> @@ -9,7 +9,7 @@
>   #include <linux/if_vlan.h>
>   
>   char e1000_driver_name[] = "e1000";

your commit message suggests that you add const "everywhere", but it
seems that there are other candidates, like the one above

PS. You have to wait 24h before posting next revision.

> -static char e1000_driver_string[] = "Intel(R) PRO/1000 Network Driver";
> +static const char e1000_driver_string[] = "Intel(R) PRO/1000 Network Driver";
>   static const char e1000_copyright[] = "Copyright (c) 1999-2006 Intel Corporation.";
>   
>   /* e1000_pci_tbl - PCI Device ID Table


  reply	other threads:[~2025-03-04  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 20:47 [PATCH v2] e1000: The 'const' qualifier has been added where applicable to enhance code safety and prevent unintended modifications joaomboni
2025-03-04  8:27 ` Przemek Kitszel [this message]
2025-03-04  9:15   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-03-04  9:13 ` Loktionov, Aleksandr

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=a17f8193-10cc-4e23-b2d1-125a336c9ce0@intel.com \
    --to=przemyslaw.kitszel@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=joaoboni017@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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