mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Piotr Hosowicz <piotr@hosowicz.com>
To: piotr@hosowicz.com
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Error in linux-2.6.37-git5 in btrfs in ctree.c
Date: Thu, 13 Jan 2011 15:29:56 +0100	[thread overview]
Message-ID: <4D2F0C64.3010403@example.com> (raw)
In-Reply-To: <4D2DB674.4030900@example.com>

On 12.01.2011 15:11, Piotr Hosowicz wrote:
> On 11.01.2011 14:14, Américo Wang wrote:
>> On Tue, Jan 11, 2011 at 01:53:55PM +0100, Piotr Hosowicz wrote:
>>> (I send again because my previous message wasn't delivered.)
>>>
>>> Hello,
>>>
>>> There is an error in here:
>>>
>>> In file included from fs/btrfs/ctree.c:21:
>>> fs/btrfs/ctree.h:1003: error: field ‘super_kobj’ has incomplete type
>>> fs/btrfs/ctree.h:1074: error: field ‘root_kobj’ has incomplete type
>>>
>>> Kernel fails to build. linux-2.6.37-git5
>
> I see that it's the same in Linus GIT tree, I didn't fail to build,
> because I corrected the same way first, it's building now. Should it be
> like that?
>

The situation is exactly the same today. What to do? I don't need btrfs, 
but must do some correction s I do not understand exactly. I don't like it.

Regards,

Piotr Hosowicz



-- 
Janusz Korwin-Mikke:
"Dyktatury dzielą się na dobre i złe. Demokracja jest zawsze głupia."
NP:  -
NB: 2.6.37-20110113-1411-pztidm+

  reply	other threads:[~2011-01-13 14:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 12:53 Piotr Hosowicz
2011-01-11 13:14 ` Américo Wang
2011-01-12 14:11   ` Piotr Hosowicz
2011-01-13 14:29     ` Piotr Hosowicz [this message]
2011-01-13 14:45       ` Stefan Schmidt
  -- strict thread matches above, loose matches on Subject: below --
2011-01-11 10:59 Piotr Hosowicz

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=4D2F0C64.3010403@example.com \
    --to=piotr@hosowicz.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiyou.wangcong@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®