From: Florian Mickler <florian@mickler.org>
To: "werner" <w.landgraf@ru.ru>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org,
maciej.rutecki@gmail.com
Subject: Re: [Bug #42669] 3.3-rc1: compiling problems nvme , l2cap_sock , mc13892-regulator , and snd-pcsp don't work
Date: Sat, 25 Feb 2012 23:48:04 +0100 [thread overview]
Message-ID: <20120225234804.5461de60@schatten.dmk.lab> (raw)
In-Reply-To: <web-701939672@zbackend1.aha.ru>
On Fri, 24 Feb 2012 17:55:07 -0400
"werner" <w.landgraf@ru.ru> wrote:
>
> >
> >> This things happens, because people, after changes, nor
> >>compile them
> >> subroutines ... :( Much less, test them ...
> >
>
>
> In -rc1 were compilation errors in several subroutines,
> and almost none of them was fixed until -rc4 .
>
> And: that's a steady problem (although I bacame tired ond
> report only exceptionally about this).
>
> Generally, people, after patching something, at least
> should try to compile the subroutine !!!!!!!!!!!!!!
And as David just told you, it compiles fine for him without the fix.
Should every developer test every available toolchain combination?
>
>
> W.Landgraf
> ---
> Professional hosting for everyone - http://www.host.ru
next prev parent reply other threads:[~2012-02-25 22:48 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 22:51 3.3-rc4+: Reported regressions from 3.2 Rafael J. Wysocki
2012-02-23 22:51 ` Rafael J. Wysocki
2012-02-23 22:51 ` [Bug #42669] 3.3-rc1: compiling problems nvme , l2cap_sock , mc13892-regulator , and snd-pcsp don't work Rafael J. Wysocki
2012-02-23 23:19 ` David Miller
2012-02-23 23:19 ` David Miller
2012-02-23 23:30 ` Rafael J. Wysocki
2012-02-23 23:30 ` Rafael J. Wysocki
2012-02-24 10:48 ` werner
2012-02-24 19:57 ` David Miller
2012-02-24 19:57 ` David Miller
2012-02-24 21:55 ` werner
2012-02-24 21:55 ` werner
2012-02-25 22:48 ` Florian Mickler [this message]
2012-02-23 22:55 ` [Bug #42686] iwlagn is getting even worse with 3.3-rc1 Rafael J. Wysocki
2012-02-23 22:55 ` Rafael J. Wysocki
2012-02-23 22:55 ` [Bug #42707] Hang deconfiguring network interface (in shutdown) on 3.3-rc1 Rafael J. Wysocki
2012-02-27 23:44 ` James Bottomley
2012-02-28 1:24 ` Matt Carlson
2012-02-28 21:07 ` David Miller
2012-02-28 21:07 ` David Miller
2012-02-28 23:32 ` Matt Carlson
2012-02-28 23:32 ` Matt Carlson
2012-02-29 0:58 ` James Bottomley
2012-02-29 0:58 ` James Bottomley
2012-02-29 9:33 ` Michael Chan
2012-02-29 18:46 ` David Miller
2012-02-29 18:46 ` David Miller
2012-02-23 22:55 ` [Bug #42683] WARN... Device 'cpu1' does not have a release() function, it is broken and must be fixed. when doing 'xl vcpu-set <guest_id> 1' Rafael J. Wysocki
2012-02-23 22:55 ` Rafael J. Wysocki
2012-02-24 4:33 ` Konrad Rzeszutek Wilk
2012-02-24 4:33 ` Konrad Rzeszutek Wilk
2012-02-23 22:55 ` [Bug #42678] [3.3-rc1] radeon stuck in kernel after lockup Rafael J. Wysocki
2012-02-24 9:14 ` Torsten Kaiser
2012-02-24 9:14 ` Torsten Kaiser
2012-02-23 22:55 ` [Bug #42735] kobject (ffff88003ffbb4b8): tried to init an initialized object, something is seriously wrong Rafael J. Wysocki
2012-02-23 22:55 ` [Bug #42713] Regression in skge that started around acb42a3 (so past v3.3-rc1) Rafael J. Wysocki
2012-02-23 22:55 ` [Bug #42733] Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed Rafael J. Wysocki
2012-02-23 22:55 ` [Bug #42734] dosemu graphics broken in v3.3-rc1 Rafael J. Wysocki
2012-02-23 22:55 ` Rafael J. Wysocki
2012-02-23 22:55 ` [Bug #42746] 3.3-rc2 snd_pcm lockdep backtrace Rafael J. Wysocki
2012-02-23 22:55 ` [Bug #42761] Possible circular locking dependency (3.3-rc2) Rafael J. Wysocki
2012-02-23 22:55 ` Rafael J. Wysocki
2012-02-23 22:55 ` [Bug #42776] OF-related boot crash in 3.3.0-rc3-00188-g3ec1e88 Rafael J. Wysocki
2012-02-23 22:55 ` [Bug #42798] i915 regression with 3.3-rc3+git Rafael J. Wysocki
2012-02-23 23:28 ` 3.3-rc4+: Reported regressions from 3.2 David Miller
2012-02-23 23:28 ` David Miller
2012-02-24 0:13 ` Rafael J. Wysocki
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=20120225234804.5461de60@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=davem@davemloft.net \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=w.landgraf@ru.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.