All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Bug fixes for makedevs.c
Date: Mon, 28 Oct 2019 21:22:41 +0000	[thread overview]
Message-ID: <1853bfbf-6129-314b-0b99-9458e917d5e1@intel.com> (raw)
In-Reply-To: <CAJ86T=WBz6OkPcOLWH2gyH8JGnC8-d2-9=TE8ThtjeD4rE+ssg@mail.gmail.com>

On 28/10/2019 19:11, Andre McCurdy wrote:
> On Mon, Oct 28, 2019 at 10:15 AM Frazer Leslie Clews
> <frazer.clews@codethink.co.uk> wrote:
>>
>> fixes a few bugs in some print statements and an overflow bug with usr_buf
>>
>> Frazer Leslie Clews (2):
>>    fix format strings in makedevs.c in print statements
>>    fix invalidScanfFormatWidth to prevent overflowing usr_buf
> 
> Perhaps fixing these issues would be a good opportunity to align with
> the Buildroot (ie upstream?) version instead of diverging even more.
> 
>    https://git.buildroot.net/buildroot/tree/package/makedevs/makedevs.c

Yes, this.

If we can just fetch makedevs from buildroot that's one less piece of 
code we have to look after.

Ross


      reply	other threads:[~2019-10-28 21:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28 17:14 [PATCH 0/2] Bug fixes for makedevs.c Frazer Leslie Clews
2019-10-28 17:14 ` [PATCH 1/2] fix format strings in makedevs.c in print statements Frazer Leslie Clews
2019-10-28 17:14 ` [PATCH 2/2] fix invalidScanfFormatWidth to prevent overflowing usr_buf Frazer Leslie Clews
2019-10-28 17:32 ` ✗ patchtest: failure for Bug fixes for makedevs.c Patchwork
2019-10-28 19:11 ` [PATCH 0/2] " Andre McCurdy
2019-10-28 21:22   ` Ross Burton [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=1853bfbf-6129-314b-0b99-9458e917d5e1@intel.com \
    --to=ross.burton@intel.com \
    --cc=openembedded-core@lists.openembedded.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.