From: Joe Perches <joe@perches.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
postmaster <postmaster@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] tty/serial: atmel: Include module.h to fix build failure
Date: Wed, 13 Jan 2016 07:06:47 -0800 [thread overview]
Message-ID: <1452697607.8586.6.camel@perches.com> (raw)
In-Reply-To: <20160113103246.GB26117@sudip-pc>
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@vger.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.
next prev parent reply other threads:[~2016-01-13 15:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 18:15 Guenter Roeck
2016-01-09 18:29 ` Greg Kroah-Hartman
2016-01-11 8:35 ` Sudip Mukherjee
2016-01-11 11:11 ` Guenter Roeck
2016-01-11 11:34 ` Sudip Mukherjee
2016-01-11 15:08 ` Paul Gortmaker
2016-01-13 5:35 ` Guenter Roeck
2016-01-13 5:44 ` Joe Perches
2016-01-13 10:32 ` Sudip Mukherjee
2016-01-13 13:06 ` Guenter Roeck
2016-01-13 15:06 ` Joe Perches [this message]
2016-01-18 16:36 ` Guenter Roeck
2016-01-18 17:04 ` Sudip Mukherjee
2016-01-18 17:17 ` Guenter Roeck
2016-01-20 5:51 ` Sudip Mukherjee
2016-01-20 6:27 ` Guenter Roeck
2016-01-20 6:32 ` Sudip Mukherjee
2016-01-13 10:29 ` Sudip Mukherjee
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=1452697607.8586.6.camel@perches.com \
--to=joe@perches.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nicolas.ferre@atmel.com \
--cc=paul.gortmaker@windriver.com \
--cc=postmaster@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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
Powered by JetHome