From: Simon Quigley <tsimonq2@ubuntu.com>
To: dsterba@suse.cz
Cc: clm@fb.com, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: backref: Fixed checkpatch warning of over 80 characters
Date: Mon, 22 Feb 2016 06:36:52 -0600 [thread overview]
Message-ID: <1456144612.3587.16.camel@ubuntu.com> (raw)
In-Reply-To: <20160222123346.GE4374@twin.jikos.cz>
> 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. :)
next prev parent reply other threads:[~2016-02-22 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 18:17 [PATCH] btrfs: backref: Fixed checkpatch warning of over 80 characters Simon Quigley
2016-02-21 0:02 ` Joe Perches
2016-02-21 0:56 ` [PATCH] btrfs: backref: Fixed checkpatch warning of over 80 Simon Quigley
2016-02-21 0:57 ` Simon Quigley
2016-02-21 1:49 ` Joe Perches
2016-02-21 2:06 ` [PATCH] btrfs: backref: Fixed checkpatch warning of over 80 characters Simon Quigley
2016-02-21 2:08 ` Simon Quigley
2016-02-22 11:57 ` David Sterba
2016-02-22 12:10 ` Simon Quigley
2016-02-22 12:33 ` David Sterba
2016-02-22 12:36 ` Simon Quigley [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-20 18:16 Simon Quigley
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=1456144612.3587.16.camel@ubuntu.com \
--to=tsimonq2@ubuntu.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@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).