public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 3/3] blkpr: add read-reservation command
Date: Wed, 17 Dec 2025 13:26:40 -0500	[thread overview]
Message-ID: <20251217182640.GA69951@fedora> (raw)
In-Reply-To: <ce5rsy5oycyuyfke6kcyrqokgim3cctjewhuv4gw2ptbkev7zh@ehw77wgurx7y>

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

On Wed, Dec 17, 2025 at 11:53:46AM +0100, Karel Zak wrote:
> On Thu, Dec 11, 2025 at 11:09:56AM -0500, Stefan Hajnoczi wrote:
> > 
> > diff --git a/meson.build b/meson.build
> > index 47b43c2af..b759e992f 100644
> > --- a/meson.build
> > +++ b/meson.build
> > @@ -768,6 +768,9 @@ conf.set('HAVE_DECL_PR_REP_CAPACITY', have ? 1 : false)
> >  have = cc.has_header_symbol('linux/pr.h', 'IOC_PR_READ_KEYS')
> >  conf.set('HAVE_DECL_IOC_PR_READ_KEYS', have ? 1 : false)
> >  
> > +have = cc.has_header_symbol('linux/pr.h', 'IOC_PR_READ_RESERVATION')
> > +conf.set('HAVE_DECL_IOC_PR_READ_RESERVATION', have ? 1 : false)
> 
> It seems you do not need to define HAVE_DECL_IOC_PR_READ_RESERVATION
> and care about this in meson.build or configure.ac.
> 
> > +#if HAVE_DECL_IOC_PR_READ_RESERVATION
> > +	{IOC_PR_READ_RESERVATION, "read-reservation",
> > +	"  * read-reservation: This command shows the current reservation.\n"},
> > +#endif
> 
> I think you can use directly
> 
>         #ifdef IOC_PR_READ_RESERVATION
> 
>         #endif
> 
> as IOC_PR_READ_RESERVATION is macro in linux/pr.h

Will fix in v2.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2025-12-17 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 16:09 [PATCH 0/3] blkpr: add read-keys and read-reservations commands Stefan Hajnoczi
2025-12-11 16:09 ` [PATCH 1/3] blkpr: prepare for _IOR() ioctls Stefan Hajnoczi
2025-12-11 16:09 ` [PATCH 2/3] blkpr: add read-keys command Stefan Hajnoczi
2025-12-11 16:09 ` [PATCH 3/3] blkpr: add read-reservation command Stefan Hajnoczi
2025-12-17 10:53   ` Karel Zak
2025-12-17 18:26     ` Stefan Hajnoczi [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=20251217182640.GA69951@fedora \
    --to=stefanha@redhat.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.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