public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Zeeshan Ahmad <zeeshanahmad022019@gmail.com>
Cc: Parthiban Veerasooran <parthiban.veerasooran@microchip.com>,
	Christian Gromm <christian.gromm@microchip.com>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Ethan Tidmore <ethantidmore06@gmail.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: most: dim2: convert pr_info/err/warn to dev_info/err/warn
Date: Sat, 7 Feb 2026 12:57:08 +0100	[thread overview]
Message-ID: <2026020726-ruckus-imperfect-6ca5@gregkh> (raw)
In-Reply-To: <2026020759-conductor-going-669d@gregkh>

On Sat, Feb 07, 2026 at 12:56:15PM +0100, Greg Kroah-Hartman wrote:
> On Sat, Feb 07, 2026 at 07:34:32AM +0500, Zeeshan Ahmad wrote:
> > The dim2 driver currently uses generic pr_* logging macros. Hardware
> > drivers should use the device-specific dev_* logging macros to provide
> > better context in the system logs, especially in systems with multiple
> > controller instances.
> > 
> > This patch converts all applicable logging calls in dim2.c to use the
> > proper device-specific APIs.
> > 
> > Signed-off-by: Zeeshan Ahmad <zeeshanahmad022019@gmail.com>
> > ---
> > v3:
> >  - Removed "staging-next" and redundant "[PATCH]" from the subject line.
> >  - Shortened commit message lines to stay under 75 characters.
> >  - Added this changelog below the "---" as suggested by Ethan Tidmore.
> >  - Cleaned up temporary submission notes from the permanent commit body.
> > v2:
> >  - Rebased against the staging-next branch.
> >  - Fixed CC list to include relevant maintainers.
> > 
> >  drivers/staging/most/dim2/dim2.c | 44 ++++++++++++++++----------------
> >  1 file changed, 22 insertions(+), 22 deletions(-)
> > 
> > diff --git a/drivers/staging/most/dim2/dim2.c b/drivers/staging/most/dim2/dim2.c
> > index 80af965356d0..4bcafda481f9 100644
> > --- a/drivers/staging/most/dim2/dim2.c
> > +++ b/drivers/staging/most/dim2/dim2.c
> > @@ -246,9 +246,9 @@ static void retrieve_netinfo(struct dim2_hdm *dev, struct mbo *mbo)
> >  {
> >  	u8 *data = mbo->virt_address;
> >  
> > -	pr_info("Node Address: 0x%03x\n", (u16)data[16] << 8 | data[17]);
> > +	dev_info(&dev->dev, "Node Address: 0x%03x\n", (u16)data[16] << 8 | data[17]);
> 
> My review comments from your v1 patch remain the same here.

And note, that's the problem with going "too fast", you spent time
respinning patches without allowing others to review the original patch.
Please slow down and send updates maybe once a week.  There is no rush
here.

thanks,

greg k-h

      reply	other threads:[~2026-02-07 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-07  2:34 [PATCH v3] staging: most: dim2: convert pr_info/err/warn to dev_info/err/warn Zeeshan Ahmad
2026-02-07  5:19 ` Ethan Tidmore
2026-02-07 11:56 ` Greg Kroah-Hartman
2026-02-07 11:57   ` Greg Kroah-Hartman [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=2026020726-ruckus-imperfect-6ca5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=christian.gromm@microchip.com \
    --cc=dan.carpenter@linaro.org \
    --cc=ethantidmore06@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=parthiban.veerasooran@microchip.com \
    --cc=zeeshanahmad022019@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