LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andreas Dilger <andreas.dilger@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH 2/6] staging: lustre: remove libcfs/linux/libcfs.h
Date: Wed, 18 Apr 2018 12:32:01 +1000 [thread overview]
Message-ID: <874lk9s0ri.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <alpine.LFD.2.21.1804160431550.16188@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]
On Mon, Apr 16 2018, James Simmons wrote:
>> This include file is only included in one place,
>> and only contains a list of other include directives.
>> So just move all those to the place where this file
>> is included, and discard the file.
>>
>> One include directive uses a local name ("linux-cpu.h"), so
>> that needs to be given a proper path.
>>
>> Probably many of these should be remove from here, and moved to
>> just the files that need them.
>
> Nak. Dumping all the extra headers from linux/libcfs.h to libcfs.h is
> the wrong approach. The one header, libcfs.h, to be the only header
> in all lustre files is the wrong approach. I have been looking to
> unroll that mess. I have patch that I need to polish you that I can
> submit.
I think we both have the same goal - maybe just different paths to get
there. If you have something nearly ready to submit, I'm happy to wait
for it, then proceed on top of it.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-04-18 2:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 0:42 [PATCH 0/6] staging: lustre: code rearrangement NeilBrown
2018-04-16 0:42 ` [PATCH 3/6] staging: lustre: remove include/linux/libcfs/linux/linux-cpu.h NeilBrown
2018-04-16 3:52 ` James Simmons
2018-04-18 2:33 ` NeilBrown
2018-04-23 13:13 ` Greg Kroah-Hartman
2018-04-16 0:42 ` [PATCH 4/6] staging: lustre: rearrange placement of CPU partition management code NeilBrown
2018-04-16 3:53 ` James Simmons
2018-04-16 0:42 ` [PATCH 1/6] staging: lustre: move stack-check macros to libcfs_debug.h NeilBrown
2018-04-16 3:48 ` James Simmons
2018-04-16 15:27 ` [lustre-devel] " Patrick Farrell
2018-04-16 22:42 ` James Simmons
2018-04-16 22:48 ` Doug Oucharek
2018-04-17 5:26 ` Dilger, Andreas
2018-04-17 15:41 ` Doug Oucharek
2018-04-18 2:29 ` NeilBrown
2018-04-18 4:23 ` Patrick Farrell
2018-04-18 2:17 ` NeilBrown
2018-04-23 13:03 ` Greg Kroah-Hartman
2018-04-16 0:42 ` [PATCH 6/6] staging: lustre: move remaining code from linux-module.c to module.c NeilBrown
2018-04-16 0:42 ` [PATCH 5/6] staging: lustre: move misc-device registration closer to related code NeilBrown
2018-04-23 13:12 ` Greg Kroah-Hartman
2018-04-16 0:42 ` [PATCH 2/6] staging: lustre: remove libcfs/linux/libcfs.h NeilBrown
2018-04-16 3:35 ` James Simmons
2018-04-18 2:32 ` NeilBrown [this message]
2018-04-23 13:03 ` 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=874lk9s0ri.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=andreas.dilger@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.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 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).