From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] PAM sanity
Date: Thu, 20 Jun 2013 17:38:22 +0100 [thread overview]
Message-ID: <1371746304-16785-1-git-send-email-ross.burton@intel.com> (raw)
Hi,
A whitespace fix for libpam, and then something more "interesting". I spent an
hour earlier cursing my build before finally realising the reason that my PAM
modules were not running on login was because the pam DISTRO_FEATURE wasn't
enabled. So, here's a patch to make libpam warn if it's being build without the
pam DISTRO_FEATURE.
Ross
Ross Burton (2):
libpam: fix whitespace in shell function
libpam: check if PAM is enabled when building
meta/recipes-extended/pam/libpam_1.1.6.bb | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-06-20 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 16:38 Ross Burton [this message]
2013-06-20 16:38 ` [PATCH 1/2] libpam: fix whitespace in shell function Ross Burton
2013-06-20 16:38 ` [PATCH 2/2] libpam: check if PAM is enabled when building Ross Burton
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=1371746304-16785-1-git-send-email-ross.burton@intel.com \
--to=ross.burton@intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox