From: Shahar Avidar <ikobh7@gmail.com>
To: gregkh@linuxfoundation.org, luca.ceresoli@bootlin.com,
benjamin.tissoires@redhat.com, elder@linaro.org,
andriy.shevchenko@linux.intel.com, robh@kernel.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Fix defines in rf69.h
Date: Wed, 28 Feb 2024 00:10:38 +0200 [thread overview]
Message-ID: <20240227221043.532938-1-ikobh7@gmail.com> (raw)
This patchset fixes several misuses of the define statement in rf69.h.
Duplicted defines.
Define in header instead of source file.
Unused define.
Using units.h macro to define frequency.
v2->v1:
- Fix grammer in commit messages.
- Use units.h macro to define frequency.
- Reorder patches to ensure no conflicts.
Shahar Avidar (5):
staging: pi433: Remove a duplicated FIFO_SIZE define
staging: pi433: Remove a duplicated F_OSC define
staging: pi433: Redefine F_OSC using units.h macro
staging: pi433: Remove the unused FREQUENCY define
staging: pi433: Move FIFO_THRESHOLD define to source file
drivers/staging/pi433/pi433_if.c | 1 +
drivers/staging/pi433/rf69.c | 4 ++--
drivers/staging/pi433/rf69.h | 4 ----
3 files changed, 3 insertions(+), 6 deletions(-)
base-commit: 455c5e12a3b7d08c2ab47b7dd54944901c69cdcd
--
2.34.1
next reply other threads:[~2024-02-27 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 22:10 Shahar Avidar [this message]
2024-02-27 22:10 ` [PATCH 1/5] staging: pi433: Remove a duplicated FIFO_SIZE define Shahar Avidar
2024-02-27 22:10 ` [PATCH 2/5] staging: pi433: Remove a duplicated F_OSC define Shahar Avidar
2024-02-27 22:10 ` [PATCH 3/5] staging: pi433: Redefine F_OSC using units.h macro Shahar Avidar
2024-02-27 22:10 ` [PATCH 4/5] staging: pi433: Remove the unused FREQUENCY define Shahar Avidar
2024-02-27 22:10 ` [PATCH 5/5] staging: pi433: Move FIFO_THRESHOLD define to source file Shahar Avidar
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=20240227221043.532938-1-ikobh7@gmail.com \
--to=ikobh7@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=elder@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=luca.ceresoli@bootlin.com \
--cc=robh@kernel.org \
/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