mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Alexander Viro <viro@math.psu.edu>
Cc: Jan Harkes <jaharkes@cs.cmu.edu>,
	linux-kernel@vger.kernel.org, kaos@ocs.com.au
Subject: Re: [PATCH] iget-locked [2/6]
Date: Sat, 11 May 2002 10:23:48 +0100	[thread overview]
Message-ID: <20020511102348.B24305@infradead.org> (raw)
In-Reply-To: <20020511030437.GA29392@ravel.coda.cs.cmu.edu> <Pine.GSO.4.21.0205102317410.20383-100000@weyl.math.psu.edu>

On Fri, May 10, 2002 at 11:44:23PM -0400, Alexander Viro wrote:
> As for the binary compatibility... as long as we are source-compatible
> (i.e. keep ->read_inode2 and provide a compatible iget4()) - compatibility
> is not a problem.  Anyone who ships binary-only modules is playing in the
> traffic and if they become a roadkill - it's Not Our Problem(tm).  Think
> of it as evolution in action...

We need to keep iget4, but I don't think keeping ->read_inode2 source
compatiblitly is needed, it always was marked as a reiserfs cludge and
no one was supposed to use it.


  reply	other threads:[~2002-05-11  9:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-10 16:07 Jan Harkes
2002-05-10 19:57 ` Alexander Viro
2002-05-10 20:00   ` Linus Torvalds
2002-05-10 20:15     ` Alexander Viro
2002-05-10 20:17       ` Linus Torvalds
2002-05-11  0:22   ` Keith Owens
2002-05-11  2:21     ` Kai Germaschewski
2002-05-11  2:48       ` Keith Owens
2002-05-11  3:04         ` Jan Harkes
2002-05-11  3:44           ` Alexander Viro
2002-05-11  9:23             ` Christoph Hellwig [this message]
2002-05-11  9:22           ` Christoph Hellwig
2002-05-11  3:06         ` Kai Germaschewski
2002-05-11  3:28           ` Keith Owens

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=20020511102348.B24305@infradead.org \
    --to=hch@infradead.org \
    --cc=jaharkes@cs.cmu.edu \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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®