From: NeilBrown <neilb@suse.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [VFS PATCH] constify more dcache.h inlined helpers.
Date: Tue, 19 Dec 2017 10:15:07 +1100 [thread overview]
Message-ID: <87po7bljb8.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20171020033319.GS21978@ZenIV.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
On Fri, Oct 20 2017, Al Viro wrote:
> On Fri, Oct 20, 2017 at 11:41:17AM +1100, NeilBrown wrote:
>> On Wed, Aug 02 2017, NeilBrown wrote:
>>
>> > Many of the inlines in dcache.h were changed to accept
>> > const struct pointers in commit f0d3b3ded999 ("constify dcache.c
>> > inlined helpers where possible").
>> > This patch allows 'const' in a couple that were added since then.
>> >
>> > Signed-off-by: NeilBrown <neilb@suse.com>
>>
>> Ping ... should I be sending this somewhere else? Is there a problem
>> with it?
>
> Nothing, just slipped through the cracks; July and August had been
> insane (move from nc.us to ma.us after well over a decade in one
> apartment; 'nuff said...)
>
> Applied.
Hi Al,
I don't see this in linux-next, but it seems to be pulling from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git
which doesn't exist any more.
I don't see it in the for-next branch of
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs
either, or in for-linus.
Where should I be looking?
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-12-18 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 3:24 NeilBrown
2017-10-20 0:41 ` NeilBrown
2017-10-20 3:33 ` Al Viro
2017-10-20 9:39 ` NeilBrown
2017-12-18 23:15 ` NeilBrown [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=87po7bljb8.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®