[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1452697607.8586.6.camel@perches.com>
Date: Wed, 13 Jan 2016 07:06:47 -0800
From: Joe Perches <joe@...ches.com>
To: Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc: Guenter Roeck <linux@...ck-us.net>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
postmaster <postmaster@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Nicolas Ferre <nicolas.ferre@...el.com>,
linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] tty/serial: atmel: Include module.h to fix build
failure
On Wed, 2016-01-13 at 16:02 +0530, Sudip Mukherjee wrote:
> On Tue, Jan 12, 2016 at 09:44:10PM -0800, Joe Perches wrote:
> > On Tue, 2016-01-12 at 21:35 -0800, Guenter Roeck wrote:
[]
> > > Sudip, one option would be to set up a semi-private mailing list.
> > > My build tests now have a dedicated virtual host (kerneltests.org).
> > > I could set up a managed list there.
> >
> > Perhaps it'd be better to have something like linux-build-failures@...r.kernel.org
>
> yes, much better. But if me and Guenter are the only two members of that
> list then it will not look nice. :)
Likely kbuild-robot output would use it.
That would be better than bcc'ing lkml.
Powered by blists - more mailing lists