All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: linux-3.10-rc1 procfs interface breaks vmware, eicon, fio .... any fix?
Date: Mon, 13 May 2013 03:04:00 +0100	[thread overview]
Message-ID: <20130513020400.GS25399@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAAJw_Zv4Cy-fSg24F=7poRNs2oGA=7nuZQtQOyf_-dsStzNpgw@mail.gmail.com>

On Mon, May 13, 2013 at 08:19:46AM +0800, Jeff Chua wrote:
> Anyone on lkml working on patches for vmware to make it run on
> Linux-3.10-rc1? The recent change in procfs interface breaks vmware,
> diva/eicon and fio modules.
> 
> Every modules is now broken and needs to be reworked. Is there a more
> subtle way to handle this like give more time to allow developers to
> handle the move rather than killing off the "tranditional" procfs
> access

I might feel bad about those, if not for one thing - their authors
had explicitly chosen to keep them out of tree and did not bother
to watch what was going on in linux-next - these changes had been
there for quite a while.  And now you have a chutzpah to come and
complain about that?  Better yet, we are expected to be working on
fixing those?  Really?  It's not a rethorical question - I seriously
want to know whether I'd misparsed what you meant to say.

  reply	other threads:[~2013-05-13  2:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13  0:19 linux-3.10-rc1 procfs interface breaks vmware, eicon, fio .... any fix? Jeff Chua
2013-05-13  2:04 ` Al Viro [this message]
2013-05-13  3:28   ` Jeff Chua

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=20130513020400.GS25399@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.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 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.