public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: Andrew Morton <akpm@linux-foundation.org>,
	Ralf Baechle <ralf@linux-mips.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix build error due to not including <linux/errno.h>
Date: Sun, 1 Apr 2007 06:58:41 +0200	[thread overview]
Message-ID: <E1HXs9J-0001TO-Nx@flower> (raw)
In-Reply-To: <20070318220148.bc223088.akpm@linux-foundation.org>

> From: Andrew Morton
> Newsgroups: gmane.linux.kernel
> Subject: Re: [PATCH] Fix build error due to not including <linux/errno.h>
> Date: Sun, 18 Mar 2007 22:01:48 -0800
>
> If is a bit of a pain to maintain CONFIG_SYSFS=n.  But then, it's
> realtively easy to fix things when they do break, and sysfs does consume
> rather a lot of memory at runtime.  Hopefully someone out there is finding
> SYSFS=n to be useful for deeply embedded applications.

Actually i've managed to build and run rc5 for five days now. Not so
embedded amd64 laptop.

Kudos and thanks to Ralf.

After splitting kobject from sysfs, as it was commented Tejun Heo in the

[RFD driver-core] Lifetime problems of the current driver model

maybe something lightweight can emerge, without current 'features' and
going-to-be sysfs-v1,v2,v3 thing...
____

      reply	other threads:[~2007-04-01  4:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-18 12:58 [PATCH] Fix build error due to not including <linux/errno.h> Ralf Baechle
2007-03-19  0:36 ` Alan Stern
2007-03-19  0:44   ` Ralf Baechle
2007-03-19  6:01     ` Andrew Morton
2007-04-01  4:58       ` Oleg Verych [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=E1HXs9J-0001TO-Nx@flower \
    --to=olecom@flower.upol.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=stern@rowland.harvard.edu \
    --cc=torvalds@linux-foundation.org \
    /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