From: David Miller <davem@davemloft.net>
To: w.landgraf@ru.ru
Cc: linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org,
maciej.rutecki@gmail.com, florian@mickler.org
Subject: Re: [Bug #42669] 3.3-rc1: compiling problems nvme , l2cap_sock , mc13892-regulator , and snd-pcsp don't work
Date: Fri, 24 Feb 2012 14:57:37 -0500 (EST) [thread overview]
Message-ID: <20120224.145737.662334352795127267.davem@davemloft.net> (raw)
In-Reply-To: <web-701709481@zbackend1.aha.ru>
From: "werner" <w.landgraf@ru.ru>
Date: Fri, 24 Feb 2012 06:48:58 -0400
> But why then the error is still in the source code, at least until the
> last 3.3-rc4 ??? I also compiled the code, removing always inline
> from the line as in the patch, then it works.
Because the fix is in the networking maintainer's tree and will shortly
be sent to Linus for inclusion.
> This things happens, because people, after changes, nor compile them
> subroutines ... :( Much less, test them ...
You need to relax.
The compile error only occurs with more recently compiler versions, so
it worked for the majority of people and in fact it compiles just fine
for me without the fix too.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: w.landgraf-ow1r9FSYgO0@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
florian-sVu6HhrpSfRAfugRpC6u6w@public.gmane.org
Subject: Re: [Bug #42669] 3.3-rc1: compiling problems nvme , l2cap_sock , mc13892-regulator , and snd-pcsp don't work
Date: Fri, 24 Feb 2012 14:57:37 -0500 (EST) [thread overview]
Message-ID: <20120224.145737.662334352795127267.davem@davemloft.net> (raw)
In-Reply-To: <web-701709481-zcyLqNHFQq3Ee+7He9zlJw@public.gmane.org>
From: "werner" <w.landgraf-ow1r9FSYgO0@public.gmane.org>
Date: Fri, 24 Feb 2012 06:48:58 -0400
> But why then the error is still in the source code, at least until the
> last 3.3-rc4 ??? I also compiled the code, removing always inline
> from the line as in the patch, then it works.
Because the fix is in the networking maintainer's tree and will shortly
be sent to Linus for inclusion.
> This things happens, because people, after changes, nor compile them
> subroutines ... :( Much less, test them ...
You need to relax.
The compile error only occurs with more recently compiler versions, so
it worked for the majority of people and in fact it compiles just fine
for me without the fix too.
next prev parent reply other threads:[~2012-02-24 19:58 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 [this message]
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
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 #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 #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 #42713] Regression in skge that started around acb42a3 (so past v3.3-rc1) 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 #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 #42735] kobject (ffff88003ffbb4b8): tried to init an initialized object, something is seriously wrong 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 #42798] i915 regression with 3.3-rc3+git 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 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=20120224.145737.662334352795127267.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=florian@mickler.org \
--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.