public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>,
	Trond Myklebust <trondmy@kernel.org>,
	 Anna Schumaker <anna@kernel.org>
Subject: Re: [PATCH] pnfs: add pnfs_ds_connect trace point
Date: Tue, 10 Jun 2025 15:55:04 +0200 (CEST)	[thread overview]
Message-ID: <1488667048.5476965.1749563704151.JavaMail.zimbra@desy.de> (raw)
In-Reply-To: <F3C7A0A4-E8DB-406A-89FF-C44CA9201D44@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 762 bytes --]



----- Original Message -----
> From: "Benjamin Coddington" <bcodding@redhat.com>
> To: "Tigran Mkrtchyan" <tigran.mkrtchyan@desy.de>
> Cc: "linux-nfs" <linux-nfs@vger.kernel.org>, "Trond Myklebust" <trondmy@kernel.org>, "Anna Schumaker" <anna@kernel.org>
> Sent: Tuesday, 10 June, 2025 14:47:23
> Subject: Re: [PATCH] pnfs: add pnfs_ds_connect trace point

> On 10 Jun 2025, at 5:34, Tigran Mkrtchyan wrote:
> 
>> this trace point aims expose pnfs ds connect status
> 
> This tracepoint aims to expose pNFS DS connect status?

Thanks, Ben.

I can send v2 if desired.

Best regards,
   Tigran.

> 
>>
>> Signed-off-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
> 
> 
> Logic looks correct,
> 
> Reviewed-by: Benjamin Coddington <bcodding@redhat.com>
> 
> Ben

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2826 bytes --]

  reply	other threads:[~2025-06-10 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10  9:34 [PATCH] pnfs: add pnfs_ds_connect trace point Tigran Mkrtchyan
2025-06-10 12:47 ` Benjamin Coddington
2025-06-10 13:55   ` Mkrtchyan, Tigran [this message]
2025-06-10 15:12 ` [PATCH v2] " Tigran Mkrtchyan

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=1488667048.5476965.1749563704151.JavaMail.zimbra@desy.de \
    --to=tigran.mkrtchyan@desy.de \
    --cc=anna@kernel.org \
    --cc=bcodding@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@kernel.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