Linux kernel staging patches
 help / color / mirror / Atom feed
From: Gustavo Piaz da Silva <gustavopiazdasilva2102@gmail.com>
To: gregkh@linuxfoundation.org, dan.carpenter@linaro.org
Cc: ovidiu.panait.oss@gmail.com, gshahrouzi@gmail.com,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Gustavo Piaz da Silva <gustavopiazdasilva2102@gmail.com>
Subject: [PATCH v8 0/2] staging: axis-fifo: clean up probe logic
Date: Mon,  9 Feb 2026 08:32:27 -0300	[thread overview]
Message-ID: <20260209113229.7871-1-gustavopiazdasilva2102@gmail.com> (raw)

This series cleans up the axis-fifo driver probe function logic.

Changes in v8:
 - Reverted line wrapping changes to keep the diff focused strictly 
   on logic refactoring and avoid unrelated whitespace noise.

Changes in v7:
 - Rewrote Patch 1 description for better clarity and acknowledged 
   that the original code works.
 - Reverted variable name and type back to 'unsigned int value' to 
   minimize diff noise.
 - Removed unnecessary whitespace and extra blank lines between 
   function calls and error checks.

Changes in v6:
 - Removed axis_fifo_get_u32() helper function entirely.
 - Removed all dev_err() calls in parse_dt.
 - Kept 'node' local variable in parse_dt to avoid checkpatch 
   line length warnings.
 - Added missing "---" line after Signed-off-by.
 - Fixed checkpatch style warning (missing blank line after declarations).
 - Ensured newline at the end of the file.

Changes in v5:
 - Added missing newline at the end of axis-fifo.c file in Patch 2.

Changes in v4:
 - Removed extra blank lines in commit messages.
 - Added "rx" and "tx" prefixes to error messages (removed in v6).

Changes in v3:
 - Split the original monolithic v2 patch into two separate patches.

Changes in v2:
 - Fixed checkpatch.pl coding style issues.

Gustavo Piaz da Silva (2):
  staging: axis-fifo: use u32 for fifo depth flags
  staging: axis-fifo: refactor device tree parsing

 drivers/staging/axis-fifo/axis-fifo.c | 59 +++++++++------------------
 1 file changed, 19 insertions(+), 40 deletions(-)

-- 
2.52.0


             reply	other threads:[~2026-02-09 11:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09 11:32 Gustavo Piaz da Silva [this message]
2026-02-09 11:32 ` [PATCH v8 1/2] staging: axis-fifo: use u32 for fifo depth flags Gustavo Piaz da Silva
2026-02-09 12:32   ` Ovidiu Panait
2026-02-09 11:32 ` [PATCH v8 2/2] staging: axis-fifo: refactor device tree parsing Gustavo Piaz da Silva
2026-02-09 12:12 ` [PATCH v8 0/2] staging: axis-fifo: clean up probe logic Dan Carpenter

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=20260209113229.7871-1-gustavopiazdasilva2102@gmail.com \
    --to=gustavopiazdasilva2102@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=gshahrouzi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=ovidiu.panait.oss@gmail.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