From: Sarah Nadi <snadi@uwaterloo.ca>
To: Grant Grundler <grantgrundler@gmail.com>
Cc: Grant Grundler <grundler@parisc-linux.org>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: Kconfig Dependencies in Linux
Date: Fri, 17 Jan 2014 16:03:34 -0500 [thread overview]
Message-ID: <52D99AA6.7080902@uwaterloo.ca> (raw)
In-Reply-To: <CAP6odjg-dTix7zZKcGmaHJAptAe7wLdD+NMVrmvOcG++d506cA@mail.gmail.com>
Hi Grant,
Thanks for your feedback. I was actually specifically targetting
developers who have committed to the Kconfig files before as far as I
could tell from the kernel's git repository rather than randomly
picking people listed in MAINTAINERS. I do have questions about certain
dependencies, but I also want to get the general intuition behind when a
Kconfig dependency is enforced, and if there is external/domain
knowledge that comes into play. This is why I was interested in talking
to developers.
In all cases, I do appreciate the advice!
Sarah
On 14-01-17 03:55 PM, Grant Grundler wrote:
> On Fri, Jan 17, 2014 at 12:05 PM, Sarah Nadi <snadi@uwaterloo.ca> wrote:
>> Hi Grant,
> Sarah,
> If you have specific questions about Kconfig files (and the rules they
> embed), my advice is to ask on linux kernel mailing list. You'll get
> the answers you are looking for.
>
> For specific projects that use the kernel, like parisc-linux or Chrome
> OS (my day job), ask on those respective mailing lists:
> linux-parisc@vger.kernel.org (cc'd)
> https://groups.google.com/a/chromium.org/forum/#!forum/chromium-os-dev
>
> Asking random people listed in MAINTAINERS is just going to get you a
> lot of negative feedback.
>
> cheers,
> grant
>
prev parent reply other threads:[~2014-01-17 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52D98D23.3010004@uwaterloo.ca>
2014-01-17 20:55 ` Kconfig Dependencies in Linux Grant Grundler
2014-01-17 21:03 ` Sarah Nadi [this message]
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=52D99AA6.7080902@uwaterloo.ca \
--to=snadi@uwaterloo.ca \
--cc=grantgrundler@gmail.com \
--cc=grundler@parisc-linux.org \
--cc=linux-parisc@vger.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.