mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: J?rn Engel <joern@wohnheim.fh-wedel.de>
Cc: Linus Torvalds <torvalds@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: [PATCH] stat nlink resolution fix
Date: Tue, 15 Jun 2004 11:20:39 -0700	[thread overview]
Message-ID: <20040615182039.GA4553@taniwha.stupidest.org> (raw)
In-Reply-To: <20040615145624.GC20432@wohnheim.fh-wedel.de>

On Tue, Jun 15, 2004 at 04:56:25PM +0200, J?rn Engel wrote:

> Just for me to get a clue, what would break if the definition of
> nlink_t changed?

It's derived from __kernel_nlink_t which is exported to userspace
(well, glibc headers).


  --cw

      reply	other threads:[~2004-06-15 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15  5:55 Chris Wedgwood
2004-06-15 14:56 ` Jörn Engel
2004-06-15 18:20   ` Chris Wedgwood [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=20040615182039.GA4553@taniwha.stupidest.org \
    --to=cw@f00f.org \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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®