virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexander Atanasov <alexander.atanasov@virtuozzo.com>
Cc: virtualization@lists.linux-foundation.org, kernel@openvz.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/1] Create debugfs file with virtio balloon usage information
Date: Tue, 9 Aug 2022 06:35:25 -0400	[thread overview]
Message-ID: <20220809063414-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <f6b46a29-0f65-9081-5228-a1028fea2bef@virtuozzo.com>

On Tue, Jul 05, 2022 at 12:01:58PM +0300, Alexander Atanasov wrote:
> > > diff --git a/include/uapi/linux/virtio_balloon.h b/include/uapi/linux/virtio_balloon.h
> > > index ddaa45e723c4..f3ff7c4e5884 100644
> > > --- a/include/uapi/linux/virtio_balloon.h
> > > +++ b/include/uapi/linux/virtio_balloon.h
> > > @@ -40,6 +40,7 @@
> > >   /* Size of a PFN in the balloon interface. */
> > >   #define VIRTIO_BALLOON_PFN_SHIFT 12
> > > +#define VIRTIO_BALLOON_PAGE_SIZE (1<<VIRTIO_BALLOON_PFN_SHIFT)
> > >   #define VIRTIO_BALLOON_CMD_ID_STOP	0
> > >   #define VIRTIO_BALLOON_CMD_ID_DONE	1
> > Did you run checkpatch on this?
> 
> 
> Sure, i did:
> 
> scripts/checkpatch.pl
> ../outgoing/v4-0001-Create-debugfs-file-with-virtio-balloon-usage-inf.patch
> total: 0 errors, 0 warnings, 108 lines checked
> 
> ../outgoing/v4-0001-Create-debugfs-file-with-virtio-balloon-usage-inf.patch
> has no obvious style problems and is ready for submission.

Weird. There should be spaces around << I think.

-- 
MST

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  parent reply	other threads:[~2022-08-09 10:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220705083638.29669-1-alexander.atanasov@virtuozzo.com>
2022-07-05  8:59 ` [PATCH v4 1/1] Create debugfs file with virtio balloon usage information Michael S. Tsirkin
     [not found]   ` <f6b46a29-0f65-9081-5228-a1028fea2bef@virtuozzo.com>
2022-08-09 10:35     ` Michael S. Tsirkin [this message]
2022-07-14 11:35 ` David Hildenbrand
     [not found]   ` <123b7518-b0c9-171c-9596-73654691ee58@virtuozzo.com>
2022-07-14 13:24     ` David Hildenbrand
     [not found]   ` <20220714132053.56323-1-alexander.atanasov@virtuozzo.com>
2022-07-18 11:35     ` [PATCH v5 " David Hildenbrand
     [not found]       ` <865e4da3-94fe-95dc-cbe3-161fa8c2146d@virtuozzo.com>
2022-07-25 11:36         ` David Hildenbrand
     [not found]           ` <20220726140831.72816-1-alexander.atanasov@virtuozzo.com>
2022-08-01 15:18             ` [PATCH v6 1/2] " David Hildenbrand
     [not found]               ` <3a5e60e8-a0d2-a1f1-28e9-e0b45069029a@virtuozzo.com>
2022-08-01 20:12                 ` David Hildenbrand
     [not found]                   ` <2dfad5c8-59d2-69a1-cc4c-d530c12ceea9@virtuozzo.com>
2022-08-02 13:48                     ` [RFC] how the ballooned memory should be accounted by the drivers inside the guests? (was:[PATCH v6 1/2] Create debugfs file with virtio balloon usage information) David Hildenbrand
     [not found]                       ` <7bfac48d-2e50-641b-6523-662ea4df0240@virtuozzo.com>
2022-08-09 10:03                         ` David Hildenbrand
     [not found]             ` <20220726141047.72913-1-alexander.atanasov@virtuozzo.com>
2022-08-01 15:13               ` [PATCH v6 2/2] Unify how inflated memory is accounted in virtio balloon driver David Hildenbrand
2022-08-09 10:42               ` Michael S. Tsirkin
2022-08-09 10:44             ` [PATCH v6 1/2] Create debugfs file with virtio balloon usage information Michael S. Tsirkin

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=20220809063414-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alexander.atanasov@virtuozzo.com \
    --cc=kernel@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).