From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: linux-media@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: [PATCH zbar 1/5] Fix autoreconf by reducing the warning/error checking
Date: Mon, 14 Jan 2019 10:43:29 -0200 [thread overview]
Message-ID: <20190114104329.7673d2b7@coco.lan> (raw)
In-Reply-To: <CADvTj4rHkTtpZLtuFtBR8GRpfZd28jL9b9ZPVd8V-eZvEQgmuw@mail.gmail.com>
Em Mon, 14 Jan 2019 05:26:42 -0700
James Hilliard <james.hilliard1@gmail.com> escreveu:
> On Mon, Jan 14, 2019 at 4:00 AM Mauro Carvalho Chehab
> <mchehab+samsung@kernel.org> wrote:
> >
> > Hi James,
> >
> > Em Mon, 14 Jan 2019 07:38:25 +0800
> > james.hilliard1@gmail.com escreveu:
> >
> > > From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > >
> >
> > Please add description to the patches. It helps reviewing them, and,
> > if we need to revert it for whatever reason in the future, the git log
> > will help to take into account the rationale about why the change was
> > needed in the first place.
> >
> > > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > > Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> > > ---
> > > configure.ac | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/configure.ac b/configure.ac
> > > index a03d10e..6476a20 100644
> > > --- a/configure.ac
> > > +++ b/configure.ac
> > > @@ -5,7 +5,7 @@ m4_ifndef([AC_LANG_DEFINES_PROVIDED],
> > > [m4_define([AC_LANG_DEFINES_PROVIDED])])
> > > AC_CONFIG_AUX_DIR(config)
> > > AC_CONFIG_MACRO_DIR(config)
> > > -AM_INIT_AUTOMAKE([1.13 -Werror foreign subdir-objects std-options dist-bzip2])
> > > +AM_INIT_AUTOMAKE([1.13 foreign subdir-objects std-options dist-bzip2])
> > > m4_pattern_allow([AM_PROG_AR])
> > > AC_CONFIG_HEADERS([include/config.h])
> > > AC_CONFIG_SRCDIR(zbar/scanner.c)
> >
> > I applied patches 2 to 5 of this series, but I would prefer to keep the
> > -Werror here, as it helps to identify and fix potential issues.
> >
> > Here (Fedora 29), everything builds fine, but I haven't test on other
> > distros that could have newer packages.
> >
> > Why is this patch needed?
> It was part of buildroot's zbar patches, not sure if it's needed though anymore.
Ok. Let's keep it without this patch. If you find any warning causing
buildroot to fail, feel free to send us a patch fixing it.
Thanks!
Mauro
prev parent reply other threads:[~2019-01-14 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-13 23:38 [PATCH zbar 1/5] Fix autoreconf by reducing the warning/error checking james.hilliard1
2019-01-13 23:38 ` [PATCH zbar 2/5] Fix function protoype to be compatible with recent libjpeg james.hilliard1
2019-01-13 23:38 ` [PATCH zbar 3/5] Add --disable-doc configure option to disable building docs james.hilliard1
2019-01-13 23:38 ` [PATCH zbar 4/5] Ignore ENOTTY errors when calling VIDIOC_S_CROP james.hilliard1
2019-01-13 23:38 ` [PATCH zbar 5/5] release video buffers after probing and request them again when needed james.hilliard1
2019-01-14 11:00 ` [PATCH zbar 1/5] Fix autoreconf by reducing the warning/error checking Mauro Carvalho Chehab
2019-01-14 12:26 ` James Hilliard
2019-01-14 12:43 ` Mauro Carvalho Chehab [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=20190114104329.7673d2b7@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=james.hilliard1@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
/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