All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sandeep Patil <sspatil@android.com>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 1/3] cve/cve-2014-0196: Don't use libutil for Android
Date: Fri, 12 Apr 2019 12:39:29 -0700	[thread overview]
Message-ID: <20190412193929.GD124555@google.com> (raw)
In-Reply-To: <20190411233115.32744-2-pvorel@suse.cz>

On Fri, Apr 12, 2019 at 01:31:13AM +0200, Petr Vorel wrote:
> From: Petr Vorel <petr.vorel@gmail.com>
> 
> as it's not available for it.
> 
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>

We've needed this for a while now and I always end up removing
the libutil reference in the auto-generated gen.bp file. Thanks for
fixing this Petr.

Acked-by: Sandeep Patil <sspatil@android.com>

  reply	other threads:[~2019-04-12 19:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 23:31 [LTP] [PATCH 0/3][RFC] Android fixes and -Werror-implicit-function-declaration as default Petr Vorel
2019-04-11 23:31 ` [LTP] [RFC PATCH 1/3] cve/cve-2014-0196: Don't use libutil for Android Petr Vorel
2019-04-12 19:39   ` Sandeep Patil [this message]
2019-04-14  9:59     ` Petr Vorel
2019-04-11 23:31 ` [LTP] [RFC PATCH 2/3] Add more missing <string.h> and <strings.h> includes Petr Vorel
2019-04-12  2:12   ` =?unknown-8bit?b?6Ziu5q2j5pe6?=
2019-04-12  8:49     ` Cyril Hrubis
2019-04-12  8:48       ` Petr Vorel
2019-04-12  9:05         ` =?unknown-8bit?b?6Ziu5q2j5pe6?=
2019-04-12  9:45           ` Cyril Hrubis
2019-04-12  9:46             ` Petr Vorel
2019-04-12 16:48           ` Enji Cooper
2019-04-11 23:31 ` [LTP] [RFC PATCH 3/3] make: Add -Werror-implicit-function-declaration for all targets Petr Vorel
2019-07-12 13:48   ` Petr Vorel
2019-08-02 13:03     ` Cyril Hrubis
2019-08-02 13:27       ` Petr Vorel

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=20190412193929.GD124555@google.com \
    --to=sspatil@android.com \
    --cc=ltp@lists.linux.it \
    /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.