From: AyushMukkanwar <ayushmukkanwar@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
AyushMukkanwar <ayushmukkanwar@gmail.com>
Subject: [PATCH v2 0/2] staging: octeon: replace pr_*() calls with dev_*() and netdev_*()
Date: Tue, 31 Mar 2026 16:47:55 +0530 [thread overview]
Message-ID: <20260331111757.110703-1-ayushmukkanwar@gmail.com> (raw)
In-Reply-To: <2026033119-endpoint-jimmy-6b83@gregkh>
Replace pr_*() calls with dev_*() and netdev_*() across the octeon
ethernet drivers to include device information in log messages, as
suggested by Greg KH.
v2:
- Instead of adding pr_fmt() macros, replace pr_*() calls with
proper dev_*() and netdev_*() calls
- Thread device pointer through call chains via function parameters
- Introduce struct octeon_ethernet_platform to pass device pointer
through work queue callbacks via container_of
- Store device pointer in oct_rx_group for NAPI poll functions
- Use dev_id in interrupt handler to pass and retrieve device pointer
AyushMukkanwar (2):
staging: octeon: ethernet-spi: replace pr_err with dev_err
staging: octeon: ethernet: replace pr_* with dev_* and netdev_*
drivers/staging/octeon/ethernet-mem.c | 26 ++++++------
drivers/staging/octeon/ethernet-mem.h | 4 +-
drivers/staging/octeon/ethernet-rx.c | 6 ++-
drivers/staging/octeon/ethernet-rx.h | 6 +--
drivers/staging/octeon/ethernet-spi.c | 59 +++++++++++++-------------
drivers/staging/octeon/ethernet.c | 61 ++++++++++++++++-----------
6 files changed, 89 insertions(+), 73 deletions(-)
--
2.53.0
next prev parent reply other threads:[~2026-03-31 11:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 13:30 [PATCH 0/3] staging: octeon: add pr_fmt macro to ethernet drivers AyushMukkanwar
2026-03-24 13:30 ` [PATCH 1/3] staging: octeon: ethernet-mem: add pr_fmt macro AyushMukkanwar
2026-03-24 13:30 ` [PATCH 2/3] staging: octeon: ethernet-spi: " AyushMukkanwar
2026-03-24 13:30 ` [PATCH 3/3] staging: octeon: ethernet: " AyushMukkanwar
2026-03-24 14:28 ` Greg KH
2026-03-25 9:03 ` Ayush Mukkanwar
2026-03-25 9:11 ` Greg KH
2026-03-25 19:12 ` Ayush Mukkanwar
2026-03-30 15:56 ` Greg KH
2026-03-31 7:16 ` Ayush Mukkanwar
2026-03-31 8:28 ` Greg KH
2026-03-31 11:17 ` AyushMukkanwar [this message]
2026-03-31 11:17 ` [PATCH v2 1/2] staging: octeon: ethernet-spi: replace pr_err with dev_err AyushMukkanwar
2026-04-01 10:09 ` Greg KH
2026-04-04 9:17 ` Ayush Mukkanwar
2026-04-04 9:20 ` Ayush Mukkanwar
2026-04-05 8:02 ` Greg KH
2026-03-31 11:17 ` [PATCH v2 2/2] staging: octeon: ethernet: replace pr_* with dev_* and netdev_* AyushMukkanwar
2026-04-01 1:10 ` kernel test robot
2026-04-01 9:32 ` 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=20260331111757.110703-1-ayushmukkanwar@gmail.com \
--to=ayushmukkanwar@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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