From: Guenter Roeck <linux@roeck-us.net>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Build regressions/improvements in v3.8-rc5
Date: Sun, 27 Jan 2013 10:48:45 -0800 [thread overview]
Message-ID: <20130127184845.GA4054@roeck-us.net> (raw)
In-Reply-To: <CA+icZUWhNQN0_H5sK7PuNuk6ObS6emyWPXg4Eun=f15t21ReMA@mail.gmail.com>
On Sun, Jan 27, 2013 at 02:56:46PM +0100, Sedat Dilek wrote:
> Hi Geert,
>
> what is the intention of this list [1] which you regularly sent to LKML?
>
> Statistics?
>
> [ Compiler errors/warnings ]
>
> Are you directly contacting the maintainers of the subtree and inform
> them (per email, website etc.?
> Do you sent or plan to send this list as a whole (single list) or
> broken-down for each subsystem?
> The latter would be have more success.
> Can you add such a per-subsystem list (compiler errors/warnings etc.)
> to kisskb service (or plan to)?
> What is your feedback from Linux kernel maintainers?
>
FWIW, I track it to see if there are any errors or warnings in the hwmon
subsystem.
Guenter
> [ In General ]
>
> What is your infrastructure (Linux OS etc.)?
> What is toolchain (compiler version etc.) do you use?
> Are those produced kernels tested on real or virtual hardware?
> Or do you test compiled-only or not?
>
> I really wish you success with your service!
>
> Thanks.
>
> Regards,
> - Sedat -
>
> [1] http://marc.info/?l=linux-kernel&m=135929071204017&w=2
>
next prev parent reply other threads:[~2013-01-27 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 13:56 Sedat Dilek
2013-01-27 18:48 ` Guenter Roeck [this message]
2013-01-27 18:51 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2013-01-27 12:44 Geert Uytterhoeven
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=20130127184845.GA4054@roeck-us.net \
--to=linux@roeck-us.net \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@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
all inboxes | Powered by JetHome®