From: "werner" <w.landgraf@ru.ru>
To: greg@kroah.com, randy.dunlap@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: easycap needs smp_lock.h, fixes build error
Date: Tue, 30 Nov 2010 18:17:31 -0400 [thread overview]
Message-ID: <web-413524031@zbackend1.aha.ru> (raw)
In-Reply-To: <20101130145740.GA11199@kroah.com>
OK For your information, the patch by r.dunlap works on
2.6.37-rc4 too, the second compilation (including the
patch) was successful.
wl
===========================
On Tue, 30 Nov 2010 06:57:40 -0800
Greg KH <greg@kroah.com> wrote:
> On Tue, Nov 30, 2010 at 10:44:21AM -0400, werner wrote:
>> HELLO
>>
>> I dont believe this ... my 2.6.37-rc4 compilation gone
>>bad again,
>> because of the same error, and I have to recompile /
>>re-package it,
>> what needs some hours again .. :( :(
>>
>> The correction below worked on 2.6.37-rc3 (i.e. insert
>>#include
>> <linux/smp_lock.h> into easycap_main.h)
>>
>>
>> WHY THIS WASN'T PATCHED SINCE LONG TIME ? Is the
>>situation of the
>> kernel developers similar bad like of the open office
>>developers, so
>> that they should be exchanged ???
>
> This is fixed in Linux-next and will be going to Linus
>in a few days.
>
> thanks,
>
> greg k-h
>
>
"werner" <w.landgraf@ru.ru>
---
Professional hosting for everyone - http://www.host.ru
prev parent reply other threads:[~2010-11-30 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 3:20 2.6.37-rc3 problems werner
2010-11-22 4:35 ` Greg KH
2010-11-22 4:56 ` Randy Dunlap
2010-11-22 5:13 ` Randy Dunlap
2010-11-22 19:47 ` Greg KH
2010-11-22 20:12 ` [PATCH] staging: easycap needs smp_lock.h, fixes build error Randy Dunlap
2010-11-30 14:44 ` werner
2010-11-30 14:57 ` Greg KH
2010-11-30 22:17 ` werner [this message]
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=web-413524031@zbackend1.aha.ru \
--to=w.landgraf@ru.ru \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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 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.