From: Enchanted Hunter <enchantedredhunter@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
andy@kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] staging: fbtft: replace sprintf with snprintf
Date: Wed, 3 Jun 2026 12:14:29 +0300 [thread overview]
Message-ID: <CAOSULed6efCh6EYdv8gbOFdPxVrjEmXV0SJC6YR+aqBKkZ4wQw@mail.gmail.com> (raw)
In-Reply-To: <ah9_utsktDp4oN9E@ashevche-desk.local>
[-- Attachment #1: Type: text/plain, Size: 2376 bytes --]
ср, 3 июн. 2026 г. в 04:13, Andy Shevchenko <andriy.shevchenko@intel.com>:
>
>
> Please, stop top-posting.
>
> On Tue, Jun 02, 2026 at 10:33:34PM +0300, Enchanted Hunter wrote:
> > I suppose I agree with you. My patch does look silly, and I regret
> wasting
> > your time. I've just started learning kernel development. Perhaps if you
> > happen to have any routine task, you could suggest something that would
> > actually be worth doing. I'm very interested in this. I will sign with my
> > real name, but I'm from Russia, and I understand that this might be a big
> > problem right now.
>
> I have this [1]. It shouldn't be a problem as long as you are not working
> for
> the OFAC sanctioned entity or tied to them in any ways.
>
>
> > вт, 2 июн. 2026 г. в 21:32, Andy Shevchenko <andy.shevchenko@gmail.com>:
> >
> > > On Tue, Jun 2, 2026 at 8:13 PM Enchanted Hunter
> > > <enchantedredhunter@gmail.com> wrote:
> > > >
> > > > Overall, it doesn't address any compiler warnings, but this is my
> first
> > > patch. I wanted to start with something concrete, and I saw an unsafe
> > > function and tried to fix it. The fact that the compilation behavior
> won't
> > > change is true, but the code will become a bit more formal — maybe
> that's a
> > > good thing.
> > >
> > > Not sure we need a churn on the working code.
> > >
> > > A process hint: Do not top-post.
> > >
> > > > пн, 1 июн. 2026 г. в 11:25, Andy Shevchenko <
> andy.shevchenko@gmail.com>:
> > > >>
> > > >> On Mon, Jun 1, 2026 at 3:44 AM Enchanted Hunter
> > > >> <enchantedredhunter@gmail.com> wrote:
> > > >> >
> > > >> > This patch replaces unsafe sprintf calls with snprintf in
> > > >> > fbtft_register_framebuffer() to prevent potential buffer overflow.
> > > >> >
> > > >> > Signed-off-by: rat1bor <enchantedredhunter@gmail.com>
> > >
> > > Another thing, use your real name and not an alias.
> > >
> > > >> Does this change address any compiler warning or something like
> that?
> > > >> At a glance I do not see any usefulness of this patch except an
> > > >> unneeded churn.
>
> [1]: https://gist.github.com/andy-shev/a2cb1ee4767d6d2f5d20db53ecb9aabc
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
> I don't work for any organizations that are under OFAC sanctions. Sorry
for the top-posting.
[-- Attachment #2: Type: text/html, Size: 3668 bytes --]
prev parent reply other threads:[~2026-06-03 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 0:43 [PATCH] staging: fbtft: replace sprintf with snprintf Enchanted Hunter
2026-06-01 5:44 ` Greg KH
2026-06-04 4:40 ` Claude review: " Claude Code Review Bot
2026-06-04 4:40 ` Claude Code Review Bot
2026-06-01 8:25 ` Andy Shevchenko
2026-06-02 17:12 ` Enchanted Hunter
2026-06-02 18:31 ` Andy Shevchenko
2026-06-02 19:33 ` Enchanted Hunter
2026-06-03 1:13 ` Andy Shevchenko
2026-06-03 9:14 ` Enchanted Hunter [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=CAOSULed6efCh6EYdv8gbOFdPxVrjEmXV0SJC6YR+aqBKkZ4wQw@mail.gmail.com \
--to=enchantedredhunter@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
/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