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:10:56 -0600 [thread overview]
Message-ID: <1456143056.3587.8.camel@ubuntu.com> (raw)
In-Reply-To: <20160222115741.GC4374@twin.jikos.cz>
[-- Attachment #1: Type: text/plain, Size: 344 bytes --]
> 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.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-22 12:11 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 [this message]
2016-02-22 12:33 ` David Sterba
2016-02-22 12:36 ` Simon Quigley
-- 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=1456143056.3587.8.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.