From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f173.google.com ([209.85.213.173]:36495 "EHLO mail-ig0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751659AbcBVMke (ORCPT ); Mon, 22 Feb 2016 07:40:34 -0500 Message-ID: <1456144612.3587.16.camel@ubuntu.com> Subject: Re: [PATCH] btrfs: backref: Fixed checkpatch warning of over 80 characters From: Simon Quigley To: dsterba@suse.cz Cc: clm@fb.com, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <20160222123346.GE4374@twin.jikos.cz> References: <1455992258-9176-1-git-send-email-tsimonq2@ubuntu.com> <20160222115741.GC4374@twin.jikos.cz> <1456143056.3587.8.camel@ubuntu.com> <20160222123346.GE4374@twin.jikos.cz> Content-Type: text/plain; charset="UTF-8" Date: Mon, 22 Feb 2016 06:36:52 -0600 Mime-Version: 1.0 Sender: linux-btrfs-owner@vger.kernel.org List-ID: > 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. :)