From: Ralf Baechle <ralf@linux-mips.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix build error due to not including <linux/errno.h>
Date: Mon, 19 Mar 2007 00:44:43 +0000 [thread overview]
Message-ID: <20070319004443.GA25164@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0703182036060.17900-100000@netrider.rowland.org>
On Sun, Mar 18, 2007 at 08:36:48PM -0400, Alan Stern wrote:
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
>
> Thank you for spotting and fixing this.
It's the second time I've fixed a CONFIG_SYSFS=n bug. Of course that
sort of thing just shouldn't happen - but the fact that in both cases
the bug wasn't noticed for a few days makes me wonder if we simply should
always enable CONFIG_SYSFS at some point.
Ralf
next prev parent reply other threads:[~2007-03-19 2:09 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 [this message]
2007-03-19 6:01 ` Andrew Morton
2007-04-01 4:58 ` Oleg Verych
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=20070319004443.GA25164@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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