All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ayush Tiwari <ayushtiw0110@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: alison.schofield@intel.com, paul@paul-moore.com, mic@digikod.net,
	fabio.maria.de.francesco@linux.intel.com,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	outreachy@lists.linux.dev, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] LANDLOCK: use kmem_cache for landlock_object
Date: Thu, 28 Mar 2024 13:27:36 +0530	[thread overview]
Message-ID: <ZgUi8G3q0DvtcIQH@ayush-HP-Pavilion-Gaming-Laptop-15-ec0xxx> (raw)
In-Reply-To: <2024032836-grief-parish-88e7@gregkh>

On Thu, Mar 28, 2024 at 07:08:04AM +0100, Greg KH wrote:
> On Thu, Mar 28, 2024 at 04:55:57AM +0530, Ayush Tiwari wrote:
> > Use kmem_cache replace kzalloc() calls with kmem_cache_zalloc() for
> > struct landlock_object and update the related dependencies.
> 
> This says what you do, but not why you want to do any of this.  Why is
> this change needed?  What benifit does it bring?
> 
> And why did you cc: the staging mailing list?
> 
> thanks,
> 
> greg k-h
Hello Greg,
Apologies for the errors. I will resend the patch with reason also for
the changes I made. Earlier I didn't mention as I thought this patch is
regarding an Issue from the Issues List. But will keep this in mind from
now. Also, apologies for CC the staging mailing lists. I won't include
it from next time if it's not needed. Thanks.

  reply	other threads:[~2024-03-28  7:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 23:25 [PATCH] LANDLOCK: use kmem_cache for landlock_object Ayush Tiwari
2024-03-27 23:43 ` Paul Moore
2024-03-28  7:53   ` Ayush Tiwari
2024-03-28 14:45     ` Mickaël Salaün
2024-03-29  2:19       ` Ayush Tiwari
2024-03-29  6:32       ` Ayush Tiwari
2024-03-28  6:08 ` Greg KH
2024-03-28  7:57   ` Ayush Tiwari [this message]
2024-03-28  6:39 ` Dan Carpenter
2024-03-29  2:14   ` Ayush Tiwari

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=ZgUi8G3q0DvtcIQH@ayush-HP-Pavilion-Gaming-Laptop-15-ec0xxx \
    --to=ayushtiw0110@gmail.com \
    --cc=alison.schofield@intel.com \
    --cc=fabio.maria.de.francesco@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mic@digikod.net \
    --cc=outreachy@lists.linux.dev \
    --cc=paul@paul-moore.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.