From: Andrew Morton <akpm@linux-foundation.org>
To: Ian Kent <raven@themaw.net>
Cc: linux-kernel@vger.kernel.org, autofs@linux.kernel.org,
linux-fsdevel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 6/7] autofs4 - use struct qstr in waitq.c
Date: Tue, 22 Jul 2008 16:13:57 -0700 [thread overview]
Message-ID: <20080722161357.802ad1a5.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080617122406.14725.84758.stgit@raven.themaw.net>
On Tue, 17 Jun 2008 20:24:06 +0800
Ian Kent <raven@themaw.net> wrote:
> From: Jeff Moyer <jmoyer@redhat.com>
>
> The autofs_wait_queue already contains all of the fields of the
> struct qstr, so change it into a qstr.
>
> This patch, from Jeff Moyer, has been modified a liitle by myself.
>
> Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
> Signed-off-by: Ian Kent <raven@themaw.net>
So this patch which had been happily sitting in -mm for a month has
suddenly broken because linux-next's three-day-old
4bce7ce7c7d0d57b78dacc3a2bd87ec63b2d9b4c has removed LOOKUP_ACCESS.
This is suboptimal.
Now what do I do?
next prev parent reply other threads:[~2008-07-22 23:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 12:23 [PATCH 1/7] autofs4 - don't make expiring dentry negative Ian Kent
2008-06-17 12:23 ` [PATCH 2/7] autofs4 - revert - redo lookup in ttfd Ian Kent
2008-06-17 12:23 ` [PATCH 3/7] autofs4 - use look aside list for lookups Ian Kent
2008-06-17 12:23 ` [PATCH 4/7] autofs4 - don't release directory mutex if called in oz_mode Ian Kent
2008-06-17 12:24 ` [PATCH 5/7] autofs4 - use lookup intent flags to trigger mounts Ian Kent
2008-06-17 12:24 ` [PATCH 6/7] autofs4 - use struct qstr in waitq.c Ian Kent
2008-07-22 23:13 ` Andrew Morton [this message]
2008-07-23 5:08 ` Ian Kent
2008-07-23 5:17 ` Andrew Morton
2008-07-23 5:24 ` Ian Kent
2008-06-17 12:24 ` [PATCH 7/7] autofs4 - fix pending mount race Ian Kent
2008-07-01 7:04 ` Andrew Morton
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=20080722161357.802ad1a5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=autofs@linux.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).