From: Greg KH <gregkh@linuxfoundation.org>
To: Manas Ghandat <ghandatmanas@gmail.com>
Cc: Linux-kernel-mentees@lists.linuxfoundation.org, anton@tuxera.com,
linkinjeon@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net,
syzbot+4768a8f039aa677897d0@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] ntfs : fix shift-out-of-bounds in ntfs_iget
Date: Tue, 8 Aug 2023 18:36:37 +0200 [thread overview]
Message-ID: <2023080811-populace-raven-96d2@gregkh> (raw)
In-Reply-To: <CAEt2hJ5icep5dF_OhuZwe0zig4VKCTKuQ0=iYfpOek7Ebp12Lw@mail.gmail.com>
On Tue, Aug 08, 2023 at 08:45:02PM +0530, Manas Ghandat wrote:
> In the above patch I have mentioned what are the changes from the version
> 1. Also since most of the lines of the patch were a change due to some
> indentation error, the whole patch appears as the diff.
As my bot said:
> > - This looks like a new version of a previously submitted patch, but you
> > did not list below the --- line any changes from the previous version.
> > Please read the section entitled "The canonical patch format" in the
> > kernel file, Documentation/process/submitting-patches.rst for what
> > needs to be done here to properly describe this.
Please read that and submit a new patch based on the requirements there.
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-08 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 4:34 [PATCH] ntfs : fix shift-out-of-bounds in ntfs_iget Manas Ghandat
2023-08-08 5:27 ` Greg KH
2023-08-08 10:29 ` [PATCH v2] " Manas Ghandat
2023-08-08 10:45 ` Greg KH
[not found] ` <CAEt2hJ5icep5dF_OhuZwe0zig4VKCTKuQ0=iYfpOek7Ebp12Lw@mail.gmail.com>
2023-08-08 16:36 ` Greg KH [this message]
2023-08-10 16:13 ` [PATCH v3] " Manas Ghandat
2023-08-10 17:32 ` Greg KH
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=2023080811-populace-raven-96d2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Linux-kernel-mentees@lists.linuxfoundation.org \
--cc=anton@tuxera.com \
--cc=ghandatmanas@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=syzbot+4768a8f039aa677897d0@syzkaller.appspotmail.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