Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: satyam@infradead.org
Cc: akpm@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [patch 27/28] Introduce U16_MAX and U32_MAX
Date: Mon, 13 Aug 2007 13:52:22 -0700 (PDT)	[thread overview]
Message-ID: <20070813.135222.62369884.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LFD.0.999.0708132039200.29609@enigma.security.iitk.ac.in>

From: Satyam Sharma <satyam@infradead.org>
Date: Mon, 13 Aug 2007 20:59:09 +0530 (IST)

> On Fri, 10 Aug 2007, David Miller wrote:
> 
> > 2) The reiserfs definition is going to define an equivalent
> >    value, so just adding an #undef and still letting reiserfs
> >    override is wrong.  Why put a common define in kernel.h
> >    if other headers still keep their own crufty copy too?
> 
> Because removing the (re-)definition of U32_MAX from in there in
> reiserfs_fs.h will break builds of all userspace users of U32_MAX and
> max_reiserfs_offset(), would it not? I haven't looked at any reiserfs
> userspace tools source code, so possibly none such (that use
> max_reiserfs_offset) exist, but I thought it better to be safe.
> I'll have a look at the reiserfs-utils package, just in case.

If this is the case then it would be better to pick different macro
names from the one's reiserfs already defines in it's header exported
userland interfaces.

Or, alternatively, make sure reiserfs's headers get the appropriate
headers and defines even when used in userspace.

      parent reply	other threads:[~2007-08-13 20:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10 21:12 [patch 27/28] Introduce U16_MAX and U32_MAX akpm
2007-08-10 22:38 ` David Miller
2007-08-10 23:41   ` Andrew Morton
2007-08-13 15:29   ` Satyam Sharma
2007-08-13 19:03     ` Satyam Sharma
2007-08-13 20:52     ` David Miller [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=20070813.135222.62369884.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=satyam@infradead.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