linux-kernel - Re: [PATCH] btrfs: backref: Fixed checkpatch warning of over 80 characters

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160222123346.GE4374@twin.jikos.cz>
Date:	Mon, 22 Feb 2016 13:33:46 +0100
From:	David Sterba <dsterba@...e.cz>
To:	Simon Quigley <tsimonq2@...ntu.com>
Cc:	dsterba@...e.cz, clm@...com, linux-btrfs@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] btrfs: backref: Fixed checkpatch warning of over 80
 characters

On Mon, Feb 22, 2016 at 06:10:56AM -0600, Simon Quigley wrote:
> > in short, whitespace-only changes do not help too much.
> 
> But they are encouraged for people who would like to get started with kernel programming, Linus
> himself says so. In the future I plan on giving more, but I wanted to get familiarized with the
> process. So I still think this should be accepted although it's just a whitespace change.

But you are getting familiarized, you sent a patch, got feedback, defend
your patches.  That's a great start, but it does not mean that the
patches end up merged. The decision is up to the maintainer(s) of the
subsystem.

Nobody will bite your head off if you do some trivial formal mistakes in
your first patch submissions. The mistakes will be pointed out, you will
be asked to resend.  Sometimes, when the mistakes or formalities are not
worth the email roundtrip, the maintainers fix it at commit time.