From: Alex Williamson <alex.williamson@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, cohuck@redhat.com
Subject: Re: [PATCH] vfio: Cleanup allowed driver naming
Date: Fri, 19 Jun 2020 07:16:17 -0600 [thread overview]
Message-ID: <20200619071617.25e46824@x1.home> (raw)
In-Reply-To: <20200619071802.GA28304@infradead.org>
On Fri, 19 Jun 2020 00:18:02 -0700
Christoph Hellwig <hch@infradead.org> wrote:
> On Thu, Jun 18, 2020 at 01:57:18PM -0600, Alex Williamson wrote:
> > No functional change, avoid non-inclusive naming schemes.
>
> Adding a bunch of overly long lines that don't change anything are
> everything but an improvement.
In fact, 3 of 5 code change lines are shorter, the other two are 3
characters longer each and arguably more descriptive. One line does now
exceed 80 columns, though checkpatch no longer cares. I'll send a v2
with that line wrapped. Thanks,
Alex
prev parent reply other threads:[~2020-06-19 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 19:57 [PATCH] vfio: Cleanup allowed driver naming Alex Williamson
2020-06-19 7:18 ` Christoph Hellwig
2020-06-19 13:16 ` Alex Williamson [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=20200619071617.25e46824@x1.home \
--to=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=hch@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).