Linux kernel staging patches
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Penkler <dpenkler@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: gpib: Modernize gpib_interface_t initialization and make static
Date: Fri, 10 Jan 2025 16:03:09 +0100	[thread overview]
Message-ID: <2025011054-amused-award-88f8@gregkh> (raw)
In-Reply-To: <20250108174121.23044-1-dpenkler@gmail.com>

On Wed, Jan 08, 2025 at 06:41:21PM +0100, Dave Penkler wrote:
> All interface drivers were using the old style initialization of
> this struct
> 
> field : value;
> 
> This generated the followng sparse warning, for example:
> agilent_82357a/agilent_82357a.c:1492:1: warning: obsolete struct initializer, use C99 syntax
> 
> Change the initialization to use the C99 syntax
> 
> .field = value;
> 
> This also resolves the checkpatch constraint of no indentation.
> 
> These structs were also not declared as static, unnecessarily polluting
> the symbol namespace and generating the following sparse warnings,
> for example:
> 
> agilent_82357a/agilent_82357a.c:1465:18: warning: symbol 'agilent_82357a_gpib_interface' was not declared. Should it be static?
> 
> Declare them as static and remove any conflicting extern declarations
> in the corresponding include files.
> 
> Signed-off-by: Dave Penkler <dpenkler@gmail.com>
> ---
> v1 -> v2 Add subsystem prefix to subject

Please test-build your changes before sending them out :(

thanks,

greg k-h

      parent reply	other threads:[~2025-01-10 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 17:41 [PATCH v2] staging: gpib: Modernize gpib_interface_t initialization and make static Dave Penkler
2025-01-09 14:48 ` kernel test robot
2025-01-09 15:46 ` kernel test robot
2025-01-09 20:09 ` kernel test robot
2025-01-10 15:03 ` Greg KH [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=2025011054-amused-award-88f8@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dpenkler@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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