From: "dpsmith.dev" <dpsmith.dev@gmail.com>
To: Jason Andryuk <jandryuk@gmail.com>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wl@xen.org>,
Anthony PERARD <anthony.perard@citrix.com>
Subject: Re: [PATCH] flask: label-pci: Allow specifying optional irq label
Date: Mon, 13 Mar 2023 17:11:17 -0400 [thread overview]
Message-ID: <d17d7b39-28ce-55a6-8d2b-fe2dfd10c38d@gmail.com> (raw)
In-Reply-To: <CAKf6xpt02aK7SWNb=xB3kKZB3Dt9UC8mMKMVz5kq96uNJvdzbQ@mail.gmail.com>
On 3/13/23 15:14, Jason Andryuk wrote:
> On Mon, Mar 13, 2023 at 2:49 PM Daniel P. Smith
> <dpsmith@apertussolutions.com> wrote:
>> On 3/13/23 13:50, Jason Andryuk wrote:
>>> usage(argCnt, argv);
>>>
>>> + if (argCnt == 4) {
>>> + pirq_label = argv[3];
>>> + } else {
>>> + pirq_label = argv[2];
>>> + }
>>> +
>>
>> style nit: space inside parens and curly brackets could be dropped or
>> should be moved to their own lines.
>
> This file doesn't follow Xen style. I think dropping the curly braces
> is fine, but the lack of spaces 'if (argCnt == 4)' should stay for
> consistency. Does that sound okay?
>
Hmm, I thought there was interest in getting everything in tree
consistent, maybe I am mistaken. I am not hard pressed to enforce the
style. Unless someone else objects, I am good with your proposal.
>>> xch = xc_interface_open(0,0,0);
>>> if ( !xch )
>>> {
>>> @@ -107,7 +114,7 @@ int main (int argCnt, char *argv[])
>>> if (fscanf(f, "%" SCNu64, &start) != 1)
>>> start = 0;
>>> if (start) {
>>> - ret = xc_flask_add_pirq(xch, start, argv[2]);
>>> + ret = xc_flask_add_pirq(xch, start, pirq_label);
>>> if (ret) {
>>> fprintf(stderr, "xc_flask_add_pirq %"PRIu64" failed: %d\n",
>>> start, ret);
>>
>> Style nits aside, LGTM.
>>
>> Acked-by: Daniel P. Smith <dpsmith@apertussolutions.com>
>
> Thanks,
> Jason
>
next prev parent reply other threads:[~2023-03-13 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 17:50 [PATCH] flask: label-pci: Allow specifying optional irq label Jason Andryuk
2023-03-13 18:48 ` Daniel P. Smith
2023-03-13 19:14 ` Jason Andryuk
2023-03-13 21:11 ` dpsmith.dev [this message]
2023-03-14 6:42 ` Jan Beulich
2023-03-14 13:20 ` Jason Andryuk
2023-03-14 14:11 ` Jan Beulich
2023-03-14 14:19 ` Jason Andryuk
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=d17d7b39-28ce-55a6-8d2b-fe2dfd10c38d@gmail.com \
--to=dpsmith.dev@gmail.com \
--cc=anthony.perard@citrix.com \
--cc=dpsmith@apertussolutions.com \
--cc=jandryuk@gmail.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.