All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	Oleg Drokin <oleg.drokin@intel.com>,
	Andreas Dilger <andreas.dilger@intel.com>
Subject: Re: [PATCH] staging/lustre: Replace jobid acquiring with per node setting
Date: Sat, 3 May 2014 19:29:45 -0400	[thread overview]
Message-ID: <20140503232945.GA15714@kroah.com> (raw)
In-Reply-To: <1398651712-5015-1-git-send-email-green@linuxhacker.ru>

On Sun, Apr 27, 2014 at 10:21:52PM -0400, Oleg Drokin wrote:
> Insted of meddling directly in process environment variables
> (which is also not possible on certain platforms due to not exported
> symbols), create jobid_name proc file to represent this info
> (to be filled by job scheduler epilogue).

That looks better, but what are you going to do about getting rid of all
of these proc files?  Just move them all at once?  I really don't like
the idea of adding new ones, and want a plan for what you all are going
to do here moving forward.

I'll take this for now, as it is better than what you are doing with the
environment variables...

thanks,

greg k-h

  reply	other threads:[~2014-05-04  0:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28  2:21 [PATCH] staging/lustre: Replace jobid acquiring with per node setting Oleg Drokin
2014-05-03 23:29 ` Greg Kroah-Hartman [this message]
2014-05-04  1:20   ` Oleg Drokin
2014-05-04  2:33     ` Greg Kroah-Hartman
2014-05-04  3:08       ` Oleg Drokin
2014-05-04  4:15         ` Greg Kroah-Hartman

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=20140503232945.GA15714@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=green@linuxhacker.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg.drokin@intel.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.