All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pranav Tyagi <pranav.tyagi03@gmail.com>
Cc: Robert Richter <rrichter@amd.com>,
	dave@stgolabs.net, jonathan.cameron@huawei.com,
	dave.jiang@intel.com, alison.schofield@intel.com,
	vishal.l.verma@intel.com, ira.weiny@intel.com,
	dan.j.williams@intel.com, linux-cxl@vger.kernel.org,
	linux-kernel@vger.kernel.org, ming.li@zohomail.com,
	peterz@infradead.org, skhan@linuxfoundation.org,
	linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH v2] cxl/memdev: automate cleanup with __free()
Date: Thu, 26 Jun 2025 15:55:52 +0100	[thread overview]
Message-ID: <2025062615-footpath-plank-b84f@gregkh> (raw)
In-Reply-To: <CAH4c4jLAfMTn6wN3wJSOQZ3mAoYC3uhswDu6c+c6v-wv8mSifQ@mail.gmail.com>

On Thu, Jun 26, 2025 at 08:02:10PM +0530, Pranav Tyagi wrote:
> Thank you for the feedback. I understand your concerns and completely
> agree with your reasoning. Please pardon my misjudgment in sending this
> patch. I am still a beginner with kernel development and learning to
> better assess what makes a meaningful contribution.

I suggest you start in drivers/staging/ which is specifically designed
for beginners to get involved without having to bother other maintainers :)

thanks,

greg k-h

  reply	other threads:[~2025-06-26 14:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23  8:38 [PATCH v2] cxl/memdev: automate cleanup with __free() Pranav Tyagi
2025-06-24 14:43 ` Jonathan Cameron
2025-06-24 15:17 ` Robert Richter
2025-06-26 14:32   ` Pranav Tyagi
2025-06-26 14:55     ` Greg KH [this message]
2025-06-26 15:12       ` Pranav Tyagi
2025-06-28  3:04 ` Dan Carpenter
  -- strict thread matches above, loose matches on Subject: below --
2025-06-27 23:03 kernel test robot

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=2025062615-footpath-plank-b84f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.li@zohomail.com \
    --cc=peterz@infradead.org \
    --cc=pranav.tyagi03@gmail.com \
    --cc=rrichter@amd.com \
    --cc=skhan@linuxfoundation.org \
    --cc=vishal.l.verma@intel.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.