All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim.Bird@sony.com <Tim.Bird@sony.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] lib: Add library function for parsing kernel config
Date: Wed, 21 Nov 2018 19:53:21 +0000	[thread overview]
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF8E0BE529@USCULXMSG03.am.sony.com> (raw)
In-Reply-To: <20181116135947.GF29013@rei.lan>

Sorry for the slow response.  Some personal issues interfered with
my work in the last week.

> -----Original Message-----
> From: Cyril Hrubis [mailto:chrubis@suse.cz]
> Hi!
> > It would be nice to use a variable name here that was not project-specific.
> >
> > In Fuego, we automatically check a few different places, but we don't
> > check a location specified by an environment variable.  However, I've
> wanted to
> > add one.  I'd prefer to use the same one as other projects, if possible.
> >
> > I'm shooting from the hip here, but how about something like:
> > KCONFIG_PATH
> > ?
> 
> Fine with me, should I switch to this one in v2?

I didn't hear back from anyone with an alternative, so I would say yes.

That variable name is something I can try to promote to other groups
and frameworks.  IMHO, this would be a nice bit of info to get from the
kernel build, or from the build system or distribution.

Thanks,
 -- Tim

  reply	other threads:[~2018-11-21 19:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15 13:44 [LTP] [PATCH] lib: Add library function for parsing kernel config Cyril Hrubis
2018-11-15 18:57 ` Cristian Marussi
2018-11-16 13:53   ` Cyril Hrubis
2018-11-15 20:16 ` Tim.Bird
2018-11-16 13:59   ` Cyril Hrubis
2018-11-21 19:53     ` Tim.Bird [this message]
2018-11-15 20:43 ` Tim.Bird
2018-11-16 13:57   ` Cyril Hrubis
2018-11-16  3:54 ` Pengfei Xu
2018-11-16  4:03   ` Tim.Bird
2018-11-16  4:57     ` Pengfei Xu
2018-11-16 14:00   ` Cyril Hrubis
2018-11-17  5:41     ` Pengfei Xu
2018-11-23  4:56 ` Sandeep Patil

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=ECADFF3FD767C149AD96A924E7EA6EAF8E0BE529@USCULXMSG03.am.sony.com \
    --to=tim.bird@sony.com \
    --cc=ltp@lists.linux.it \
    /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.