From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Kent Overstreet <kmo@daterainc.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.10.6-rt3
Date: Fri, 16 Aug 2013 09:01:51 +0200 [thread overview]
Message-ID: <520DCE5F.1040402@linutronix.de> (raw)
In-Reply-To: <20130815152210.5ed93696@gandalf.local.home>
On 08/15/2013 09:22 PM, Steven Rostedt wrote:
> On Thu, 15 Aug 2013 11:42:55 -0700
> Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU> wrote:
>
>> On 08/12/2013 09:34 AM, Sebastian Andrzej Siewior wrote:
>>> Dear RT folks!
>>>
>>> I'm pleased to announce the v3.10.6-rt3 patch set.
>>
>> I'm getting this when trying to build:
>>
>> drivers/md/bcache/request.c: In function 'cached_dev_write_complete':
>> drivers/md/bcache/request.c:1008:2: error: implicit declaration of
>> function 'up_read_non_owner' [-Werror=implicit-function-declaration]
>> up_read_non_owner(&dc->writeback_lock);
>> ^
>> drivers/md/bcache/request.c: In function 'request_write':
>> drivers/md/bcache/request.c:1034:2: error: implicit declaration of
>> function 'down_read_non_owner' [-Werror=implicit-function-declaration]
>> down_read_non_owner(&dc->writeback_lock);
>> ^
>> cc1: some warnings being treated as errors
>>
>
> Can you send us your config.
The problem is that bcache is using new semaphore functions which it
just introduced which rt does not know about. The comment above their
definition says that it is wrong to use them and completion is the
right way to do it.
So my question is, why don't we use completion but this nasty hack?
>
> Thanks,
>
> -- Steve
Sebastian
next prev parent reply other threads:[~2013-08-16 7:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 16:34 [ANNOUNCE] 3.10.6-rt3 Sebastian Andrzej Siewior
2013-08-12 19:48 ` Steven Rostedt
2013-08-13 0:47 ` Paul Gortmaker
2013-08-13 1:03 ` Steven Rostedt
2013-08-13 1:12 ` Carsten Emde
2013-08-13 10:54 ` Thomas Gleixner
2013-08-13 12:08 ` Steven Rostedt
[not found] ` <CAF+KLxsGtt_+0shjSGbjC4MG7i_yg1NL1zUXuVb-RiN=C44_nA@mail.gmail.com>
2013-08-14 18:17 ` Sebastian Andrzej Siewior
2013-08-14 18:21 ` Staffan Tjernstrom
2013-08-15 18:42 ` Fernando Lopez-Lezcano
2013-08-15 19:22 ` Steven Rostedt
2013-08-15 19:39 ` Fernando Lopez-Lezcano
2013-08-16 7:01 ` Sebastian Andrzej Siewior [this message]
2013-08-19 17:23 ` Fernando Lopez-Lezcano
2013-08-20 0:29 ` Steven Rostedt
2013-08-20 0:34 ` Fernando Lopez-Lezcano
2013-08-20 1:02 ` Steven Rostedt
2013-08-20 7:14 ` Sebastian Andrzej Siewior
2013-08-20 14:06 ` Steven Rostedt
2013-08-20 18:58 ` Fernando Lopez-Lezcano
[not found] ` <CAFfPn7iqf5EntPKdRO3cFhd=PFostp3mVLGEtt3ksLQHonMhkw@mail.gmail.com>
2013-08-27 16:19 ` Steven Rostedt
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=520DCE5F.1040402@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=kmo@daterainc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=nando@ccrma.Stanford.EDU \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).