All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: mhiramat@kernel.org
Cc: LinuxKernel <linux-kernel@vger.kernel.org>
Subject: Bootconfig ..too many deep level of header file
Date: Sun, 21 Mar 2021 08:38:56 +0530	[thread overview]
Message-ID: <20210321030855.GA18105@debian> (raw)

 Hey, Masami

 I was wondering why so many level of "deep nesting" of a particualr header
 file like this one :

 ✔ ~/git-linux/linux/tools/bootconfig/include/linux [patch L|✔]
08:34 $ cat bootconfig.h
/* SPDX-License-Identifier: GPL-2.0 */
#ifndef _BOOTCONFIG_LINUX_BOOTCONFIG_H
#define _BOOTCONFIG_LINUX_BOOTCONFIG_H

#include "../../../../include/linux/bootconfig.h"

#endif

I am surely missing some basic stuff...but...anyway, I have taken a peek on other files in the same dir and none have the nesting like that(the include ../ ...line)

Any specific reason? OR did you thought of keeping all the header file in one paplace(wildly guessing) ...


~Bhaskar

             reply	other threads:[~2021-03-21  3:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-21  3:08 Bhaskar Chowdhury [this message]
2021-03-21 13:17 ` Bootconfig ..too many deep level of header file Masami Hiramatsu

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=20210321030855.GA18105@debian \
    --to=unixbhaskar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@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.