From: David Sterba <dsterba@suse.cz>
To: Seraphime Kirkovski <kirkseraph@gmail.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.com, jbacik@fb.com, clm@fb.com
Subject: Re: [PATCH 2/4] Btrfs: coding style fixes
Date: Tue, 20 Dec 2016 17:25:45 +0100 [thread overview]
Message-ID: <20161220162545.GN3620@twin.jikos.cz> (raw)
In-Reply-To: <20161215133805.25681-1-kirkseraph@gmail.com>
On Thu, Dec 15, 2016 at 02:38:05PM +0100, Seraphime Kirkovski wrote:
> This eliminates the rare uses of `unsigned` instead of `unsigned int`.
As far as I'm concerned, I don't like this change. It's fine to
encourage 'unsigned int' in new code, but changing the existing ones
does not sound very useful to me as there's no common preference among
the developers.
prev parent reply other threads:[~2016-12-20 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 13:38 [PATCH 2/4] Btrfs: coding style fixes Seraphime Kirkovski
2016-12-20 16:25 ` David Sterba [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=20161220162545.GN3620@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=kirkseraph@gmail.com \
--cc=linux-btrfs@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).