From: Dan Carpenter <error27@gmail.com>
To: Alfie Varghese <alfievarghese22@gmail.com>
Cc: neil.armstrong@linaro.org, gregkh@linuxfoundation.org,
linux-media@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: media: meson: vdec: fix advanced concurrency and UAF bugs
Date: Tue, 14 Jul 2026 10:15:44 +0300 [thread overview]
Message-ID: <alXiIGfZjTeaD7gm@stanley.mountain> (raw)
In-Reply-To: <20260713181602.773-1-alfievarghese22@gmail.com>
Please slow down. Wait 24 hours between resends. Otherwise it's like
we are hovering over you watching you work and holding your hand for
the tricky bits. It is overwhelming for maintainers.
Follow the other v2 rules as well:
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/
Also say that you are using AI and haven't tested these.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <error27@gmail.com>
To: Alfie Varghese <alfievarghese22@gmail.com>
Cc: neil.armstrong@linaro.org, gregkh@linuxfoundation.org,
linux-media@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: media: meson: vdec: fix advanced concurrency and UAF bugs
Date: Tue, 14 Jul 2026 10:15:44 +0300 [thread overview]
Message-ID: <alXiIGfZjTeaD7gm@stanley.mountain> (raw)
In-Reply-To: <20260713181602.773-1-alfievarghese22@gmail.com>
Please slow down. Wait 24 hours between resends. Otherwise it's like
we are hovering over you watching you work and holding your hand for
the tricky bits. It is overwhelming for maintainers.
Follow the other v2 rules as well:
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/
Also say that you are using AI and haven't tested these.
regards,
dan carpenter
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-07-14 7:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 18:16 [PATCH v2] staging: media: meson: vdec: fix advanced concurrency and UAF bugs Alfie Varghese
2026-07-13 18:16 ` Alfie Varghese
2026-07-13 18:33 ` sashiko-bot
2026-07-13 19:37 ` Ferass El Hafidi
2026-07-13 19:37 ` Ferass El Hafidi
2026-07-14 7:15 ` Dan Carpenter [this message]
2026-07-14 7:15 ` Dan Carpenter
2026-07-14 13:59 ` kernel test robot
2026-07-14 13:59 ` kernel test robot
2026-07-14 14:23 ` kernel test robot
2026-07-14 14:23 ` 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=alXiIGfZjTeaD7gm@stanley.mountain \
--to=error27@gmail.com \
--cc=alfievarghese22@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=neil.armstrong@linaro.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 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.