From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Александр Бураков" <a.burakov@rosalinux.ru>
Cc: Frank Haverkamp <haver@linux.ibm.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH 2/2] misc: genwqe: card_dev: Array index overflow fix in ddcb_cmd_fixups()
Date: Thu, 8 Dec 2022 14:16:53 +0100 [thread overview]
Message-ID: <Y5HjxaC8HcVRvOW+@kroah.com> (raw)
In-Reply-To: <1315574310.3286650.1670496901569.JavaMail.zimbra@rosalinux.ru>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Dec 08, 2022 at 01:55:01PM +0300, Александр Бураков wrote:
> Hello!
>
> The subject was created this way due to technical issues. There is only one patch here.
Great, then please fix up those issues and resend a version 2 of this
patch, otherwise it confuses us all. Please remember that we optimize
for review, and as such, if you make a mistake like this, it's up to you
to fix it up, not us.
thanks,
greg k-h
next prev parent reply other threads:[~2022-12-08 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 14:18 [PATCH] media: v4l2-flash: fix NULL dereference in v4l2_flash_s_ctrl() Aleksandr Burakov
2022-12-07 14:18 ` [PATCH 2/2] misc: genwqe: card_dev: Array index overflow fix in ddcb_cmd_fixups() Aleksandr Burakov
2022-12-07 16:23 ` Greg Kroah-Hartman
2022-12-08 10:55 ` Александр Бураков
2022-12-08 13:16 ` Greg Kroah-Hartman [this message]
2023-01-16 21:01 ` [PATCH] media: v4l2-flash: fix NULL dereference in v4l2_flash_s_ctrl() Sakari Ailus
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=Y5HjxaC8HcVRvOW+@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=a.burakov@rosalinux.ru \
--cc=arnd@arndb.de \
--cc=haver@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
/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®