linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
	arjan@infradead.org, linux-kernel@vger.kernel.org,
	jtk@us.ibm.com, wtaber@us.ibm.com, pbadari@us.ibm.com,
	markv@us.ibm.com, gregkh@us.ibm.com,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] fs: Restore files_lock and set_fs_root exports
Date: Thu, 6 Jan 2005 18:02:27 -0800	[thread overview]
Message-ID: <20050107020227.GV1292@us.ibm.com> (raw)
In-Reply-To: <20050106152621.395f935e.akpm@osdl.org>

On Thu, Jan 06, 2005 at 03:26:21PM -0800, Andrew Morton wrote:
> 
> Guys, the technical arguments are all of course correct.  But the fact
> remains that we broke things without any notice.  (Yes, perhaps someone did
> say something at sometime, but the affected party didn't know, and it's our
> job to make sure that they knew).  (These exports were removed in October -
> the IBM guys need to work out why it took so long to detect the breakage).

Indeed!

We are getting lists of symbols used by the various products, as well
as working to get them tested more frequently against kernel.org trees
instead of only against distro releases.  IBM being what it is, -finding-
all such products is a challenge, but so it goes.

							Thanx, Paul

  parent reply	other threads:[~2005-01-07  2:07 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
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             ` Paul E. McKenney [this message]
2005-01-07  1:01           ` [PATCH] fs: Restore files_lock and set_fs_root exports 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=20050107020227.GV1292@us.ibm.com \
    --to=paulmck@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=gregkh@us.ibm.com \
    --cc=jtk@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markv@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).