All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: mingo@elte.hu, viro@parcelfarce.linux.theplanet.co.uk,
	paulmck@us.ibm.com, arjan@infradead.org,
	linux-kernel@vger.kernel.org, jtk@us.ibm.com, wtaber@us.ibm.com,
	pbadari@us.ibm.com, markv@us.ibm.com, greghk@us.ibm.com,
	torvalds@osdl.org
Subject: Re: [PATCH] fs: Restore files_lock and set_fs_root exports
Date: Fri, 7 Jan 2005 22:19:05 +0000	[thread overview]
Message-ID: <20050107221905.GA17567@infradead.org> (raw)
In-Reply-To: <20050107140034.46aec534.akpm@osdl.org>

On Fri, Jan 07, 2005 at 02:00:34PM -0800, Andrew Morton wrote:
> No, I'd say that unexports are different.  They can clearly break existing
> code and so should only be undertaken with caution, and with lengthy notice
> if possible.

As mentioned before we only unexported symbols were we were pretty clear
that all users of it are indeep utterly broken.  I got about a dozend
replies for this patches, and for more than half of it where the reporter
was either the author or the module was opensource I could help them to
actually fix their code.  In this case the code is far more broken than
the others, but we've even been trying to help them fix their code for
more than a year, but IBM folks have been constanly refusing.

> The cost to us of maintaining those two lines of code for a year is
> basically zero.

But as long as IBM people don't fix their %$^%! they'll continue annoying
us and the Distibutors about adding more and more hacks for it, and other
people will write similarly crappy code using it again and making the
removal even more difficult. 

> > <sarcasm>
> > <osdl-salespitch>
> > Unfortunately you don't have the financial and political powers IBM
> > has, so your opinion doesn't matter as much.  Maybe you should become
> > OSDL member to influence the direction of Linux development.
> > </osdl-salespitch>
> > </sarcasm>
> 
> Christoph, it would be better to constraint yourself to commenting on other
> people's actions rather than entering into premature speculation regarding
> their motivations, especially when that speculation involves accusations of
> corruption.

Hey, you got messages in this thread from half a dozen kernel contributors
here and still stand against all of them and for IBM who's violating our
copyrights that don't allow non-propritary derived works from it which
any user of these deeply-internal modules clearly is.

I don't know nor care nor want to speculate over anyones motives, but the
situation is at least strange enough to deserve a little sarcastic anekdote.


  reply	other threads:[~2005-01-07 22:26 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 19:05 [PATCH] fs: Restore files_lock and set_fs_root exports Paul E. McKenney
2005-01-06 19:13 ` Christoph Hellwig
2005-01-06 20:07   ` Paul E. McKenney
2005-01-06 20:13     ` Christoph Hellwig
2005-01-06 20:35   ` Mike Waychison
2005-01-06 20:59     ` Christoph Hellwig
2005-01-06 21:35       ` Greg KH
2005-01-06 19:14 ` Al Viro
2005-01-06 20:13   ` Paul E. McKenney
2005-01-06 19:20 ` Arjan van de Ven
2005-01-06 20:15   ` Paul E. McKenney
2005-01-06 20:32     ` Al Viro
2005-01-06 21:04       ` Paul E. McKenney
2005-01-06 21:24         ` Al Viro
2005-01-06 23:26           ` Andrew Morton
2005-01-06 23:11             ` Alan Cox
2005-01-07  0:24               ` Linus Torvalds
2005-01-07  0:48                 ` Christoph Hellwig
2005-01-07  7:38                 ` Arjan van de Ven
2005-01-06 23:41             ` Christoph Hellwig
2005-01-07  0:29               ` Andrew Morton
2005-01-07  0:26                 ` Christoph Hellwig
2005-01-07  3:30                   ` Mike Waychison
2005-01-07  9:00                   ` Ingo Molnar
2005-01-07  9:15                     ` Christoph Hellwig
2005-01-07 12:14                       ` Antonio Vargas
2005-01-07 22:00                       ` Andrew Morton
2005-01-07 22:19                         ` Christoph Hellwig [this message]
2005-01-07 22:58                           ` Andrew Morton
2005-01-08 15:45                             ` Alan Cox
2005-01-07 22:49                         ` Alan Cox
2005-01-08  0:12                           ` Andrew Morton
2005-01-08  2:20                             ` Paul E. McKenney
2005-01-07 23:32                         ` Adrian Bunk
2005-01-08 13:10                           ` Al Viro
2005-01-07  1:34                 ` Alan Cox
2005-01-07  3:17                   ` Andrew Morton
2005-01-07  8:12                     ` Christoph Hellwig
2005-01-06 23:56             ` [PATCH] add feature-removal-schedule.txt documentation Greg KH
2005-01-07  0:23               ` Christoph Hellwig
2005-01-07  0:32                 ` Greg KH
2005-01-07 17:02               ` Randy.Dunlap
2005-01-07 17:54                 ` Linus Torvalds
2005-01-07 18:11                   ` Greg KH
2005-01-11 12:23                     ` [PATCH] cpufreq 2.4 interface removal schedule [Was: Re: [PATCH] add feature-removal-schedule.txt documentation] Dominik Brodowski
2005-01-12 18:41                       ` Greg KH
2005-01-07 23:58                 ` [PATCH] add feature-removal-schedule.txt documentation Dominik Brodowski
2005-01-12 18:41                 ` Greg KH
2005-01-08 18:32               ` Paul E. McKenney
2005-01-08 21:46                 ` Alan Cox
2005-01-08 23:03                   ` Arjan van de Ven
2005-01-09  6:23                     ` Paul E. McKenney
2005-01-09  6:27                   ` Paul E. McKenney
2005-01-07  2:02             ` [PATCH] fs: Restore files_lock and set_fs_root exports Paul E. McKenney
2005-01-07  1:01           ` Paul E. McKenney
2005-01-07  1:20             ` Al Viro
2005-01-13  2:51             ` Paul E. McKenney
2005-01-13  7:35               ` Arjan van de Ven
2005-01-13 17:53                 ` Paul E. McKenney
2005-01-13 17:07               ` Greg KH
2005-01-13 17:44                 ` Paul E. McKenney
2005-01-13 17:55                   ` Greg KH
2005-01-13 18:29                     ` Paul E. McKenney
2005-01-07  7:33         ` Arjan van de Ven
2005-01-07  8:15           ` Christoph Hellwig
2005-01-07 15:12           ` Paul E. McKenney
2005-01-07 15:23             ` Arjan van de Ven
2005-01-07 15:34               ` Paul E. McKenney
2005-01-07 15:56                 ` Arjan van de Ven

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=20050107221905.GA17567@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=greghk@us.ibm.com \
    --cc=jtk@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markv@us.ibm.com \
    --cc=mingo@elte.hu \
    --cc=paulmck@us.ibm.com \
    --cc=pbadari@us.ibm.com \
    --cc=torvalds@osdl.org \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=wtaber@us.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.