public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Vegard Nossum <vegard.nossum@oracle.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Christian Brauner <brauner@kernel.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-doc@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>,
	Waiman Long <longman@redhat.com>
Subject: Re: [PATCH v2] dcache: remove unnecessary NULL check in dget_dlock()
Date: Wed, 13 Dec 2023 16:09:34 +0100	[thread overview]
Message-ID: <e07c1f0f-19e3-4af8-9d57-fa66d50edec2@oracle.com> (raw)
In-Reply-To: <20231213150515.GM1674809@ZenIV>


On 13/12/2023 16:05, Al Viro wrote:
> On Wed, Dec 13, 2023 at 03:40:33PM +0100, Vegard Nossum wrote:
>> [Fixed up a couple of bad addresses in Cc]
>>
>> Hi,
>>
>> I didn't get a response to this v2 of the patch below and I don't see it
>> in vfs.git.
>>
>> Was there something wrong or is it just awaiting review? Is there
>> anything I can do or help with? I would be happy to try to review other
>> patches if there is anything outstanding.
> 
> commit 1b6ae9f6e6c3e3c35aad0f11b116a81780b8aa03 (work.dcache)
> Author: Vegard Nossum <vegard.nossum@oracle.com>
> Date:   Mon Nov 6 14:44:17 2023 +0100
> 
>      dcache: remove unnecessary NULL check in dget_dlock()
> 

Ahh, there are two vfs.git -- my bad. Thanks!


Vegard

      reply	other threads:[~2023-12-13 15:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 13:44 [PATCH v2] dcache: remove unnecessary NULL check in dget_dlock() Vegard Nossum
2023-12-13 14:40 ` Vegard Nossum
2023-12-13 15:05   ` Al Viro
2023-12-13 15:09     ` Vegard Nossum [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=e07c1f0f-19e3-4af8-9d57-fa66d50edec2@oracle.com \
    --to=vegard.nossum@oracle.com \
    --cc=brauner@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=npiggin@gmail.com \
    --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