mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Drokin, Oleg" <oleg.drokin@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Boqun Feng <boqun.feng@gmail.com>,
	"<linux-fsdevel@vger.kernel.org>" <linux-fsdevel@vger.kernel.org>,
	"<devel@driverdev.osuosl.org>" <devel@driverdev.osuosl.org>,
	"<linux-kernel@vger.kernel.org>" <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	"Dilger, Andreas" <andreas.dilger@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 1/2] vfs: export symbol 'getname' and 'putname'
Date: Wed, 22 Apr 2015 06:27:11 +0000	[thread overview]
Message-ID: <498CF73A-6CB4-4C17-8953-B4AAA855A3DF@intel.com> (raw)
In-Reply-To: <20150422055311.GB3731@infradead.org>

On Apr 22, 2015, at 1:53 AM, Christoph Hellwig wrote:

> Nak on exporting symbols for broken staging code.  Please get rid of
> the ioctls looking up path names in horrible ways in the lustre code.

For a reference, is there a good example of a non-horrible way to look up a pathname?

Thanks.

Bye,
   Oleg

  reply	other threads:[~2015-04-22  6:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22  3:50 [PATCH 0/2] staging: lustre: Replace ll_getname with vfs' getname Boqun Feng
2015-04-22  3:50 ` [PATCH 1/2] vfs: export symbol 'getname' and 'putname' Boqun Feng
2015-04-22  5:53   ` Christoph Hellwig
2015-04-22  6:27     ` Drokin, Oleg [this message]
2015-04-22  6:31       ` Christoph Hellwig
2015-04-22  6:49         ` Drokin, Oleg
2015-04-22  7:34           ` Christoph Hellwig
2015-04-24  2:38             ` Drokin, Oleg
2015-04-22  6:31     ` Greg Kroah-Hartman
2015-04-22  6:40       ` Drokin, Oleg
2015-04-22  3:50 ` [PATCH 2/2] staging: lustre: replace ll_{get,put}name() with {get,put}name() Boqun Feng
2015-04-22  5:45   ` Dilger, Andreas

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=498CF73A-6CB4-4C17-8953-B4AAA855A3DF@intel.com \
    --to=oleg.drokin@intel.com \
    --cc=andreas.dilger@intel.com \
    --cc=boqun.feng@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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®