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] [day] [month] [year] [list]

Message-ID: <1456144612.3587.16.camel@ubuntu.com>
Date:	Mon, 22 Feb 2016 06:36:52 -0600
From:	Simon Quigley <tsimonq2@...ntu.com>
To:	dsterba@...e.cz
Cc:	clm@...com, linux-btrfs@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] btrfs: backref: Fixed checkpatch warning of over 80
 characters

> 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.

So let's wait for a response from Chris. :)