All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: ally heev <allyheev@gmail.com>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: fix uninitialized pointers with free attr
Date: Wed, 19 Nov 2025 00:31:22 -0800	[thread overview]
Message-ID: <aR2AWjHTtCszByqX@infradead.org> (raw)
In-Reply-To: <231f839b3b567f16360ad2a24f51add1d40ea575.camel@gmail.com>

On Wed, Nov 19, 2025 at 12:26:56PM +0530, ally heev wrote:
> As per the ongoing discussion
> https://lore.kernel.org/lkml/58fd478f408a34b578ee8d949c5c4b4da4d4f41d.camel@HansenPartnership.com/
> , I believe there are no changes required here

What about just dropping that __free thing that just make the code
harder to read and more buggy?

  reply	other threads:[~2025-11-19  8:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 14:14 [PATCH] scsi: fix uninitialized pointers with free attr Ally Heev
2025-11-05 14:21 ` James Bottomley
2025-11-05 14:46   ` Dan Carpenter
2025-11-05 15:32     ` James Bottomley
2025-11-06 14:46       ` Dan Carpenter
2025-11-06 16:06         ` James Bottomley
2025-11-18  6:17           ` Dan Carpenter
2025-11-18 13:21             ` James Bottomley
2025-11-18 14:22               ` Dan Carpenter
2025-11-19  6:56                 ` ally heev
2025-11-19  8:31                   ` Christoph Hellwig [this message]
2025-11-19 12:43                     ` James Bottomley
2025-11-20  4:15 ` Martin K. Petersen

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=aR2AWjHTtCszByqX@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=allyheev@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.