public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: elendil@planet.nl, linux-kernel@vger.kernel.org, mel@csn.ul.ie,
	torvalds@linux-foundation.org
Subject: Re: [PATCH][BUILDERR] mm: Fix build error with !CONFIG_HUGETLBFS
Date: Wed, 11 Feb 2009 01:22:03 +0100	[thread overview]
Message-ID: <200902110122.04974.elendil@planet.nl> (raw)
In-Reply-To: <B5B23369-BEA0-4420-9967-28ABC53B3C4B@kernel.crashing.org>

Kumar Gala wrote:
> might be slightly better as:
> 
> #define hugetlb_file_setup(name,size,acctflag)  ERR_PTR(-ENOSYS)
> 
> otherwise ack.

Yes, I see. Better to take the patch from Stefan Richter then:
http://lkml.org/lkml/2009/2/10/396

      reply	other threads:[~2009-02-11  0:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 22:51 [PATCH][BUILDERR] mm: Fix build error with !CONFIG_HUGETLBFS Frans Pop
2009-02-10 22:57 ` Kumar Gala
2009-02-11  0:22   ` Frans Pop [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=200902110122.04974.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    --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