From: Dave Hansen <dave@sr71.net>
To: linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, Dave Hansen <dave@sr71.net>
Subject: [PATCH 0/3] General Kconfig reorganization
Date: Fri, 31 Jan 2014 09:24:43 -0800 [thread overview]
Message-ID: <20140131172443.2EDC06E7@viggo.jf.intel.com> (raw)
Changes from last version:
* Change one sentence in the existing SECCOMP description to be
the text that Ingo wants.
This continues in a series of patches to clean up the
configuration menus. I believe they've become really hard to
navigate and there are some simple things we can do to make
things easier to find.
next reply other threads:[~2014-01-31 17:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 17:24 Dave Hansen [this message]
2014-01-31 17:24 ` [PATCH 1/3] kconfig: consolidate arch-specific seccomp options Dave Hansen
2014-01-31 17:24 ` [PATCH 2/3] Kconfig: collapse initrd in to own menu Dave Hansen
2014-01-31 17:24 ` [PATCH 3/3] Kconfig: organize memory-related config options Dave Hansen
2014-01-31 17:24 ` Dave Hansen
2014-02-04 16:02 ` Dave Hansen
2014-02-04 16:02 ` Dave Hansen
2014-02-04 16:14 ` Michal Hocko
2014-02-04 16:14 ` Michal Hocko
2014-02-01 19:12 ` [PATCH 0/3] General Kconfig reorganization Linus Torvalds
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=20140131172443.2EDC06E7@viggo.jf.intel.com \
--to=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.