mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Xin Chen <xin.chen2@oss.qualcomm.com>
Cc: jirislaby@kernel.org, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org, liulzhao@qti.qualcomm.com,
	cheng.jiang@oss.qualcomm.com, cxin@qti.qualcomm.com
Subject: Re: [PATCH v1] tty: n_tty: use kvzalloc/kvfree for line discipline data
Date: Tue, 18 Aug 2026 08:05:38 +0200	[thread overview]
Message-ID: <2026081849-camisole-enchilada-f5f8@gregkh> (raw)
In-Reply-To: <03ebb6a0-2a3d-4260-afec-15e7e9925842@oss.qualcomm.com>

On Tue, Aug 18, 2026 at 11:09:49AM +0800, Xin Chen wrote:
> 
> On 8/17/2026 10:14 PM, Greg KH wrote:
> > What do you mean "target kernel"?  This is for 7.3-final, right?
> 
> Sorry for the confusion. This patch is based on linux-next 7.2.0-rc7,
> targeting 7.2-final (or 7.3 if the merge window has already closed).
> The wording "target kernel" was poor; what I meant is that
> kvzalloc(sizeof(*ldata), GFP_KERNEL) is used intentionally to keep
> this patch cleanly backportable to kernels older than v6.6 where
> kvzalloc_obj() is not yet available.

That doesn't matter when getting patches merged, otherwise no one would
ever use the newer and proper apis.  Please write code for Linus's tree
first.  Worry about older kernels later after changes are merged
properly.

thanks,

greg k-h

  reply	other threads:[~2026-08-18  6:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 13:55 Xin Chen
2026-08-17 14:14 ` Greg KH
2026-08-18  3:09   ` Xin Chen
2026-08-18  6:05     ` Greg KH [this message]
2026-08-18  6:22       ` Xin Chen
2026-08-17 14:16 ` Greg KH
2026-08-17 14:49   ` Greg KH
2026-08-18  6:02     ` Xin Chen
2026-08-18  6:34       ` Greg KH
2026-08-18  6:58         ` Xin Chen
2026-08-18  7:34           ` Greg KH
2026-08-21  8:06             ` Xin Chen
2026-08-18  3:31   ` Xin Chen
2026-08-18  6:07     ` Greg KH
2026-08-18  6:39       ` Xin Chen
2026-08-18  7:03 ` [PATCH v2] " Xin Chen
2026-08-18  7:15   ` Jiri Slaby
2026-08-18  7:23     ` Xin Chen
2026-08-21  6:48   ` kernel test robot
2026-08-21  8:35   ` 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=2026081849-camisole-enchilada-f5f8@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cheng.jiang@oss.qualcomm.com \
    --cc=cxin@qti.qualcomm.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=liulzhao@qti.qualcomm.com \
    --cc=xin.chen2@oss.qualcomm.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
all inboxes | Powered by JetHome®