public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ravi Kumar Kairi <kumarkairiravi@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: dpenkler@gmail.com, kuba@kernel.org, rmk+kernel@armlinux.org.uk,
	broonie@kernel.org, arnd@arndb.de, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] staging:gpib: Fix error message formatting and adjust memory allocation style
Date: Wed, 19 Feb 2025 22:34:47 +0530	[thread overview]
Message-ID: <Z7YPL19NcVG7loqt@pronto> (raw)
In-Reply-To: <2025021908-fraction-impulse-7bcb@gregkh>

On Wed, Feb 19, 2025 at 04:52:13PM +0100, Greg KH wrote:
> On Mon, Feb 17, 2025 at 06:26:15PM +0530, Ravi Kumar kairi wrote:
> > From: Ravi Kumar Kairi <kumarkairiravi@gmail.com>
> > 
> > This patch series includes two minor improvements:
> > 1. Updates the error message format for invalid base I/O addresses to use hexadecimal notation.
> > 2. Changes the memory allocation style for `private_data` to use pointer dereference rather than hardcoding the struct type.
> >    which is perfered by checkpatch.
> > 
> > Ravi Kumar Kairi (2):
> >   staging:gpib:hp_82335: Fix error message format for invalid base IO
> >     address
> >   staging:glib:hp_82335: Refactor kzalloc size calculation to use
> >     pointer dereference
> > 
> >  drivers/staging/gpib/hp_82335/hp82335.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > -- 
> > 2.48.1
> > 
> > 
> 
> No longer applies to my tree :(

yeah, I you applied another patch that fixes same issues, I just noticed
it, guess I was late. anyway have a great night/day.

regards,
Ravi

      reply	other threads:[~2025-02-19 17:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 12:56 [PATCH 0/2] staging:gpib: Fix error message formatting and adjust memory allocation style Ravi Kumar kairi
2025-02-17 12:56 ` [PATCH 1/2] [PATCH 1/2] staging:gpib:hp_82335: Fix error message format for invalid base IO address Ravi Kumar kairi
2025-02-17 12:56 ` [PATCH 2/2] [PATCH 2/2] staging:glib:hp_82335: Refactor kzalloc size calculation to use pointer dereference Ravi Kumar kairi
2025-02-18 13:04   ` Dan Carpenter
2025-02-19 15:52 ` [PATCH 0/2] staging:gpib: Fix error message formatting and adjust memory allocation style Greg KH
2025-02-19 17:04   ` Ravi Kumar Kairi [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=Z7YPL19NcVG7loqt@pronto \
    --to=kumarkairiravi@gmail.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=dpenkler@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=rmk+kernel@armlinux.org.uk \
    /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