From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/3] video: Use scnprintf() for avoiding potential buffer overflow
Date: Tue, 31 Mar 2020 13:59:32 +0200 [thread overview]
Message-ID: <9c3c20d5-290f-2a2c-07c1-12df8d02c921@samsung.com> (raw)
In-Reply-To: <s5hftdufbm9.wl-tiwai@suse.de>
On 3/27/20 9:25 AM, Takashi Iwai wrote:
> On Fri, 20 Mar 2020 14:42:51 +0100,
> Bartlomiej Zolnierkiewicz wrote:
>>
>>
>> On 3/19/20 4:49 PM, Takashi Iwai wrote:
>>> On Wed, 11 Mar 2020 10:32:27 +0100,
>>> Takashi Iwai wrote:
>>>>
>>>> Hi,
>>>>
>>>> here is a series of trivial patches just to convert suspicious
>>>> snprintf() usages with the more safer one, scnprintf().
>>>>
>>>>
>>>> Takashi
>>>>
>>>> ===
>>>>
>>>> Takashi Iwai (3):
>>>> video: omapfb: Use scnprintf() for avoiding potential buffer overflow
>>>> video: omap2: Use scnprintf() for avoiding potential buffer overflow
>>>> video: uvesafb: Use scnprintf() for avoiding potential buffer overflow
>>>>
>>>> drivers/video/fbdev/omap/omapfb_main.c | 14 +++++++-------
>>>> drivers/video/fbdev/omap2/omapfb/omapfb-sysfs.c | 8 ++++----
>>>> drivers/video/fbdev/uvesafb.c | 2 +-
>>>> 3 files changed, 12 insertions(+), 12 deletions(-)
>>>
>>> Just a gentle ping about those patches.
>>> Let me know if any further changes needed.
>> Patches #1-3 queued for v5.7, thanks!
>
> I still don't see those in linux-next as of today.
> Could you check it?
They are in drm-misc/drm-misc-next branch but for some reason linux-next
uses drm-misc/for-linux-next one.
Daniel, is this correct?
[ I couldn't find anything about for-linux-next branch at
https://drm.pages.freedesktop.org/maintainer-tools/drm-misc.html ]
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-03-31 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200311093230.24900-1-tiwai@suse.de>
[not found] ` <CGME20200319154932eucas1p2ef5a13ed2630d236acb7a7bb0b5e56c6@eucas1p2.samsung.com>
[not found] ` <s5hh7ykuyyg.wl-tiwai@suse.de>
2020-03-20 13:42 ` [PATCH 0/3] video: Use scnprintf() for avoiding potential buffer overflow Bartlomiej Zolnierkiewicz
2020-03-27 8:25 ` Takashi Iwai
2020-03-31 11:59 ` Bartlomiej Zolnierkiewicz [this message]
2020-03-31 12:10 ` Daniel Vetter
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=9c3c20d5-290f-2a2c-07c1-12df8d02c921@samsung.com \
--to=b.zolnierkie@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).