From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH] autofs: update to current patchlevel
Date: Tue, 19 Mar 2013 16:40:32 +0100 [thread overview]
Message-ID: <514886F0.9040601@opendreambox.org> (raw)
In-Reply-To: <20130319124909.GA6165@windriver.com>
On 19.03.2013 13:49, Joe MacDonald wrote:
> [[oe] [meta-networking][PATCH] autofs: update to current patchlevel] On 13.03.19 (Tue 11:24) Andreas Oberritter wrote:
>
>> * Apply all patches from ftp.kernel.org/pub/linux/daemons/autofs/v5/patches-5.0.8/
>>
>> Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
>> ---
>> .../autofs-5.0.7-add-symlink-pseudo-option.patch | 217 +++++++++
>> ...witch_conf-to-not-contain-automount-lines.patch | 50 +++
>> ...s-5.0.7-depricate-nosymlink-pseudo-option.patch | 40 ++
>> ...-5.0.7-document-browse-option-in-man-page.patch | 46 ++
>> ....0.7-dont-fail-on-master-map-self-include.patch | 59 +++
>> ....7-dont-schedule-new-alarms-after-readmap.patch | 69 +++
>> ...ent-d_type-to-filter-out-files-in-scandir.patch | 41 ++
>> ...s-5.0.7-fix-automounter-support-on-parisc.patch | 24 +
>> ...descriptor-leak-when-reloading-the-daemon.patch | 179 ++++++++
>> ...utofs-5.0.7-fix-init-script-status-return.patch | 39 ++
>> .../autofs-5.0.7-fix-libtirpc-build-option.patch | 66 +++
>> ...-fix-map-entry-duplicate-offset-detection.patch | 37 ++
>> ...ofs-5.0.7-fix-nobind-man-page-description.patch | 46 ++
>> .../autofs-5.0.7-fix-requires-in-spec-file.patch | 37 ++
>> .../autofs-5.0.7-fix-submount-offset-delete.patch | 45 ++
>> ...ofs-5.0.7-fix-systemd-unidir-in-spec-file.patch | 72 +++
>> ....7-fix-use-get_proximity-without-libtirpc.patch | 54 +++
>> ...s-5.0.7-fix-wildcard-multi-map-regression.patch | 225 ++++++++++
>> ...e-WITH_LDAP-conditional-around-LDAP-types.patch | 448 +++++++++++++++++++
>> ...-5.0.7-make-yellow-pages-support-optional.patch | 15 +-
>> ...odules-replicated-use-sin6.addr-s6_addr32.patch | 39 ++
>> .../autofs-5.0.7-update-kernel-include-files.patch | 92 ++++
>> ...-protocol-ids-instead-of-protoent-structs.patch | 471 ++++++++++++++++++++
>> ...karound-missing-GNU-versionsort-extension.patch | 149 +++++++
>> .../recipes-daemons/autofs/autofs_5.0.7.bb | 25 +-
>> 25 files changed, 2582 insertions(+), 3 deletions(-)
>
> I had started to ask why we wouldn't just update to 5.0.8 directly
> instead of patching our way there. Then I thought I'd look myself and
> now I know. :-)
>
> This is just a simple (and wholesale) integration of the patches already
> upstream? That seems reasonable to me.
Yes.
In the future, maybe we should switch to Git. A repository for autofs is
available at
git://git.kernel.org/pub/scm/linux/storage/autofs/autofs.git. For now, I
didn't want to change the recipe too much.
One of these patches fixed a problem, where the automount daemon would
hang after receiving SIGHUP, but I don't know which one exactly.
Regards,
Andreas
next prev parent reply other threads:[~2013-03-19 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 10:24 [meta-networking][PATCH] autofs: update to current patchlevel Andreas Oberritter
2013-03-19 12:49 ` Joe MacDonald
2013-03-19 15:40 ` Andreas Oberritter [this message]
2013-03-19 18:11 ` Joe MacDonald
2013-03-19 16:38 ` Khem Raj
2013-03-19 16:51 ` Andreas Oberritter
2013-03-21 18:10 ` Joe MacDonald
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=514886F0.9040601@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-devel@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 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.