All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sumitra Sharma <sumitraartsy@gmail.com>
To: outreachy@lists.linux.dev
Cc: johan@kernel.org, elder@kernel.org, gregkh@linuxfoundation.org,
	greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Sumitra Sharma <sumitraartsy@gmail.com>
Subject: [PATCH 0/3] Staging: greybus: Convert macro definitions to
Date: Thu, 23 Mar 2023 02:01:04 -0700	[thread overview]
Message-ID: <cover.1679558269.git.sumitraartsy@gmail.com> (raw)

Convert macros to a static inline function, to make the relevant 
types apparent in the definition and to benefit from the type 
checking performed by the compiler at call sites.

Sumitra Sharma (3):
  Staging: greybus: Convert macro gpio_chip_to_gb_gpio_controller to an
    inline function
  Staging: greybus: Convert macro struct gb_audio_manager_module to an
    inline function
  Staging: greybus: Convert macro struct pwm_chip_to_gb_pwm_chip to an
    inline function

 drivers/staging/greybus/audio_manager_module.c | 7 +++++--
 drivers/staging/greybus/gpio.c                 | 7 +++++--
 drivers/staging/greybus/pwm.c                  | 6 ++++--
 3 files changed, 14 insertions(+), 6 deletions(-)

-- 
2.25.1


             reply	other threads:[~2023-03-23  9:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23  9:01 Sumitra Sharma [this message]
2023-03-23  9:03 ` [PATCH 1/3] Staging: greybus: Convert macro gpio_chip_to_gb_gpio_controller to an inline function Sumitra Sharma
2023-03-23  9:03 ` [PATCH 2/3] Staging: greybus: Convert macro struct gb_audio_manager_module " Sumitra Sharma
2023-03-23  9:03 ` [PATCH 3/3] Staging: greybus: Convert macro struct pwm_chip_to_gb_pwm_chip " Sumitra Sharma
2023-03-23 17:36 ` [PATCH 0/3] Staging: greybus: Convert macro definitions to Alison Schofield

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=cover.1679558269.git.sumitraartsy@gmail.com \
    --to=sumitraartsy@gmail.com \
    --cc=elder@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@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 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.