Date: Sat, 13 Jan 2018 01:31:53 -0800 From: Eitan Adler <lists@eitanadler.com> To: Warner Losh <imp@bsdimp.com> Cc: Dimitry Andric <dim@freebsd.org>, Ed Schouten <ed@nuxi.nl>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: 1 << 31 redux Message-ID: <CAF6rxg=zRAR6AWgxcjijHPm6mA7BwmaimQ60=75qfUCjepogfg@mail.gmail.com> In-Reply-To: <CANCZdfqcmaW21K=SJz5yRbZE56njQNF6gYhLu17qMumggqA3Cw@mail.gmail.com> References: <CAF6rxg=GbfpBfPAAJg0RvpMrWW8p%2B0Ayf_Zd9i7Em2kOijFCjA@mail.gmail.com> <CABh_MKmy3ojYO3M6YwH2wWrEp5a4C-o2XC1icN%2BNj3GDo4f%2BZA@mail.gmail.com> <CA37BE71-935C-4349-AFEF-B98160460FFE@FreeBSD.org> <CANCZdfqcmaW21K=SJz5yRbZE56njQNF6gYhLu17qMumggqA3Cw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11 January 2018 at 07:47, Warner Losh <imp@bsdimp.com> wrote: > > > If we can't get people to fix the warnings we have in the tree now > (especially the kernel), why enable new warnings that will just be ignored? > We've been doing a reasonable job with warnings until now. Either way, at higher warnings levels we should add what we can. -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxg=zRAR6AWgxcjijHPm6mA7BwmaimQ60=75qfUCjepogfg>