From: "Michael S. Tsirkin" <mst@redhat.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio_balloon: coding style fixes
Date: Thu, 15 Jan 2015 15:44:12 +0200 [thread overview]
Message-ID: <20150115134412.GA23874@redhat.com> (raw)
In-Reply-To: <20150115130642.GC7008@dhcp22.suse.cz>
On Thu, Jan 15, 2015 at 02:06:42PM +0100, Michal Hocko wrote:
> On Thu 15-01-15 13:39:06, Michael S. Tsirkin wrote:
> > Most of our code has
> > struct foo {
> > }
> >
> > Fix two instances where balloon is inconsistent.
>
> I hate to complain but is it really necessary to post such patches to
> linux-api?
Well it's human to err, so it seems wise to copy parties
interested in the ABI/API whenever we are changing files under include/uapi.
Whitespace changes should mostly be safe, but it's not unknown
e.g. to include unrelated changes in the same commit by mistake.
> I thought the list was primarily for API related discussions.
Basically this line in MAINTAINERS
ABI/API
L: linux-api@vger.kernel.org
F: Documentation/ABI/
F: include/linux/syscalls.h
F: include/uapi/
F: kernel/sys_ni.c
normally means "send all patches affecting files under include/uapi/ to
this list", does it not?
Wasn't this the intent?
> This is not the only mail sent here which doesn't fall into that
> category IMO. It is far from low volume list for quite some time.
>
> Please let's get back low volume and API only discussion!
Maybe send patch dropping include/uapi/ from there,
should help drive the volumes down?
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > include/uapi/linux/virtio_balloon.h | 3 +--
> > drivers/virtio/virtio_balloon.c | 3 +--
> > 2 files changed, 2 insertions(+), 4 deletions(-)
> >
> > diff --git a/include/uapi/linux/virtio_balloon.h b/include/uapi/linux/virtio_balloon.h
> > index be40f70..4b0488f 100644
> > --- a/include/uapi/linux/virtio_balloon.h
> > +++ b/include/uapi/linux/virtio_balloon.h
> > @@ -36,8 +36,7 @@
> > /* Size of a PFN in the balloon interface. */
> > #define VIRTIO_BALLOON_PFN_SHIFT 12
> >
> > -struct virtio_balloon_config
> > -{
> > +struct virtio_balloon_config {
> > /* Number of pages host wants Guest to give up. */
> > __le32 num_pages;
> > /* Number of pages we've actually got in balloon. */
> > diff --git a/drivers/virtio/virtio_balloon.c b/drivers/virtio/virtio_balloon.c
> > index 3176ea4..0413157 100644
> > --- a/drivers/virtio/virtio_balloon.c
> > +++ b/drivers/virtio/virtio_balloon.c
> > @@ -44,8 +44,7 @@ static int oom_pages = OOM_VBALLOON_DEFAULT_PAGES;
> > module_param(oom_pages, int, S_IRUSR | S_IWUSR);
> > MODULE_PARM_DESC(oom_pages, "pages to free on OOM");
> >
> > -struct virtio_balloon
> > -{
> > +struct virtio_balloon {
> > struct virtio_device *vdev;
> > struct virtqueue *inflate_vq, *deflate_vq, *stats_vq;
> >
> > --
> > MST
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> --
> Michal Hocko
> SUSE Labs
next prev parent reply other threads:[~2015-01-15 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 11:39 [PATCH] virtio_balloon: coding style fixes Michael S. Tsirkin
2015-01-15 13:06 ` Michal Hocko
2015-01-15 13:44 ` Michael S. Tsirkin [this message]
[not found] ` <20150115134412.GA23874-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-01-15 14:13 ` Michal Hocko
2015-01-15 18:50 ` Michael S. Tsirkin
[not found] ` <20150115185018.GA31068-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-01-15 20:16 ` Michal Hocko
2015-01-15 21:09 ` Michael Kerrisk (man-pages)
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=20150115134412.GA23874@redhat.com \
--to=mst@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--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).