From: Greg KH <gregkh@linuxfoundation.org>
To: Ajay Kaher <ajay.kaher@broadcom.com>
Cc: Kuntal Nayak <kuntal.nayak@broadcom.com>,
stable@vger.kernel.org, jslaby@suse.com,
linux-kernel@vger.kernel.org, alexey.makhalov@broadcom.com,
vasavi.sirnapalli@broadcom.com, Yangxi Xiang <xyangxi5@gmail.com>,
stable <stable@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>
Subject: Re: [PATCH v4.19-v5.4] vt: fix memory overlapping when deleting chars in the buffer
Date: Mon, 1 Apr 2024 11:37:36 +0200 [thread overview]
Message-ID: <2024040149-countable-ecosystem-ee44@gregkh> (raw)
In-Reply-To: <CAD2QZ9aJtFpXWYRVmgJRjad6qXXECvi+-J++QAR2t4opa6cdUA@mail.gmail.com>
On Mon, Apr 01, 2024 at 02:51:55PM +0530, Ajay Kaher wrote:
> On Sat, Mar 30, 2024 at 2:37 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Fri, Mar 29, 2024 at 12:12:08PM -0700, Kuntal Nayak wrote:
> > > From: Yangxi Xiang <xyangxi5@gmail.com>
> > >
> > > [ upstream commit 39cdb68c64d8 ]
> >
> > Please use the full git id in the future, it makes it easier and our
> > tools want it that way so that we can tell the difference between a
> > "Fixes:" tag and an actual backport. I'll go queue this up now, thanks!
> >
>
> Thanks Greg for accepting the patch.
>
> ./scripts/checkpatch.pl confuse developers, as it gives error/warning
> if we use full git id.
No need to run checkpatch on backports, as the changelog text should not
be an issue.
> Example:
> ERROR: Please use git commit description style 'commit <12+ chars of
> sha1> ("<title line>")' - ie: 'commit e26d3009efda ("netfilter:
> nf_tables: disallow timeout for anonymous sets")'
> #6:
> commit e26d3009efda338f19016df4175f354a9bd0a4ab upstream.
>
> Or shall we have something ./scripts/checkpatchstable.pl or
> ./scripts/checkpatch.pl stable (pass argument)?
Nah, it's never come up before now, I don't think people actually run
it, and I know I've never done so or even noticed, so all is fine.
thanks,
greg k-h
prev parent reply other threads:[~2024-04-01 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 19:12 [PATCH v4.19-v5.4] vt: fix memory overlapping when deleting chars in the buffer Kuntal Nayak
2024-03-30 9:07 ` Greg KH
2024-04-01 9:21 ` Ajay Kaher
2024-04-01 9:37 ` Greg KH [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=2024040149-countable-ecosystem-ee44@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ajay.kaher@broadcom.com \
--cc=alexey.makhalov@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=jslaby@suse.com \
--cc=kuntal.nayak@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vasavi.sirnapalli@broadcom.com \
--cc=xyangxi5@gmail.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.