Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Sep 2017 10:37:55 -0600
From:      Ian Lepore <ian@freebsd.org>
To:        John Baldwin <jhb@freebsd.org>, Sean Bruno <sbruno@freebsd.org>
Cc:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r323518 - head/sys/conf
Message-ID:  <1505320675.32063.123.camel@freebsd.org>
In-Reply-To: <2493527.d9eFbJjTgo@ralph.baldwin.cx>
References:  <201709130356.v8D3u4ve095428@repo.freebsd.org> <9497208.8lqLTVLir6@ralph.baldwin.cx> <af97fd40-d3ff-6917-e9db-51f1e401ff80@freebsd.org> <2493527.d9eFbJjTgo@ralph.baldwin.cx>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2017-09-13 at 09:26 -0700, John Baldwin wrote:
> On Wednesday, September 13, 2017 09:09:42 AM Sean Bruno wrote:
> > 
> > 
> > On 09/13/17 08:35, John Baldwin wrote:
> > > 
> > > On Wednesday, September 13, 2017 03:56:04 AM Sean Bruno wrote:
> > > > 
> > > > Author: sbruno
> > > > Date: Wed Sep 13 03:56:03 2017
> > > > New Revision: 323518
> > > > URL: https://svnweb.freebsd.org/changeset/base/323518
> > > > 
> > > > Log:
> > > >   Jenkins i386 LINT build uses NOTES to generate its LINT kernel config.
> > > >   
> > > >   ixl(4) isn't in here either, so I'll remove lio(4) too.
> > > ixl missing is a bug, please put it in sys/amd64/conf/NOTES (or better yet,
> > > just fix the build on !amd64)
> > > 
> > 
> > In the case of lio(4), Cavium is explicitly not compiling for 32 bit
> > architectures.  I'm inquiring to find out if they want to build on the
> > other 64bit architectures we have.
> > 
> > In the case of ixl(4), Intel has said that this is not supported on
> > 32bit architectures.
> > 
> > I'm unsure what the best course of action is.
> The bug is more if drivers aren't in NOTES at all.  Any thing listed in
> sys/conf/files.* should be in some NOTES file, either sys/conf/NOTES for
> things that are MI or sys/${arch}/conf/NOTES for things that are MD.
> 

Didn't somebody start a task list of things for junior hackers to work
on?  Writing a script/tool to verify the assertion in that last
sentence seems like a good candidate for such a list.

-- Ian



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1505320675.32063.123.camel>