From: Matt Wilson <msw@linux.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ben Cressey <bcressey@amazon.com>,
xen-devel@lists.xenproject.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Matt Wilson <msw@amazon.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: [PATCH] minios: Fix xenbus_rm() calls in frontend drivers
Date: Fri, 6 Sep 2013 09:24:16 -0700 [thread overview]
Message-ID: <20130906162413.GA25128@u109add4315675089e695.ant.amazon.com> (raw)
In-Reply-To: <1378458029.14745.74.camel@kazak.uk.xensource.com>
On Fri, Sep 06, 2013 at 10:00:29AM +0100, Ian Campbell wrote:
> On Thu, 2013-09-05 at 11:06 -0700, Matt Wilson wrote:
> > On Thu, Sep 05, 2013 at 10:17:21AM +0100, Ian Campbell wrote:
> > > On Wed, 2013-09-04 at 17:25 -0700, Matt Wilson wrote:
[...]
> > > > char path[strlen(dev->backend) + 1 + 5 + 1];
> > > > - char nodename[strlen(dev->nodename) + 1 + 5 + 1];
> > > > + char nodename[strlen(dev->nodename) + 1 + 13 + 1];
> > >
> > > These changes don't seem to be covered by the commit message? I assume
> > > they relate to the length of the longest suffix which we are appending,
> > > perhaps using strlen("some-string-const") would make this more obvious?
> >
> > Yes, those are length related changes. I'd like to keep the code as-is
> > (following the established pattern) for this round
>
> Why? What is the benefit to keeping it this way when you are changing it
> anyway?
This should be cleaned up everywhere in a separate patch. There are
many other places where mini-os uses the existing pattern.
[msw@carbon mini-os]$ git grep ') + 1 +' | wc -l
27
http://wiki.xenproject.org/wiki/Submitting_Xen_Patches#Break_down_your_patches
"Don't mix clean-up patches (which make things look prettier or move
things round but don't change functionality) with code-change
patches. Clean-up patches should be clearly marked as having no
functional changes."
--msw
next prev parent reply other threads:[~2013-09-06 16:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 0:25 [PATCH] minios: Fix xenbus_rm() calls in frontend drivers Matt Wilson
2013-09-05 9:17 ` Ian Campbell
2013-09-05 18:06 ` Matt Wilson
2013-09-06 9:00 ` Ian Campbell
2013-09-06 16:24 ` Matt Wilson [this message]
2013-09-06 16:53 ` Ian Campbell
2013-09-06 19:52 ` [PATCH v2 0/4] minios: various cleanups and fixes Matt Wilson
2013-09-06 19:52 ` [PATCH v2 1/4] minios: correct char array allocation for xenbus paths Matt Wilson
2013-09-09 14:00 ` Ian Campbell
2013-09-09 18:53 ` Samuel Thibault
2013-09-06 19:52 ` [PATCH v2 2/4] minios: clean up allocation of char arrays used " Matt Wilson
2013-09-09 14:02 ` Ian Campbell
2013-09-06 19:52 ` [PATCH v2 3/4] minios: clean up unneeded "err = NULL" in frontend drivers Matt Wilson
2013-09-06 19:52 ` [PATCH v2 4/4] minios: fix xenbus_rm() calls " Matt Wilson
2013-09-09 14:04 ` [PATCH v2 0/4] minios: various cleanups and fixes Ian Campbell
2013-09-10 10:48 ` Ian Campbell
2013-09-05 18:17 ` [PATCH] minios: Fix xenbus_rm() calls in frontend drivers Samuel Thibault
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=20130906162413.GA25128@u109add4315675089e695.ant.amazon.com \
--to=msw@linux.com \
--cc=Ian.Campbell@citrix.com \
--cc=bcressey@amazon.com \
--cc=msw@amazon.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=stefano.stabellini@eu.citrix.com \
--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 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).