From: Greg KH <greg@kroah.com>
To: Paul H <paul@mybboard.net>
Cc: Paul H <paul@mybb.com>, Belisko Marek <marek.belisko@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: ft1000: fix spaces around comparisons in ft1000_debug.c
Date: Tue, 2 Dec 2014 17:31:05 -0800 [thread overview]
Message-ID: <20141203013105.GA21642@kroah.com> (raw)
In-Reply-To: <CAO7UptcspiZCNi8smcmhOWM9Rdn+QYHPJYmZb90A-_3sJ4wYqQ@mail.gmail.com>
On Tue, Dec 02, 2014 at 07:10:41PM -0600, Paul H wrote:
> A tutorial I read suggested using a different branch for applying the
> patches; I named it "fix-spaces". It would appear it is mistaken
> then?
You have to make your patch against the linux-next tree, not Linus's
tree, so as to not duplicate other people's work that has already been
accepted.
You can name your branch whatever you want to, that doesn't matter :)
greg k-h
next prev parent reply other threads:[~2014-12-03 1:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 15:11 [PATCH] Staging: ft1000: fix spaces around comparisons in ft1000_debug.c Paul Hedman
2014-12-03 0:48 ` Greg KH
2014-12-03 1:10 ` Paul H
2014-12-03 1:31 ` Greg KH [this message]
2014-12-03 1:34 ` Paul H
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=20141203013105.GA21642@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.belisko@gmail.com \
--cc=paul@mybb.com \
--cc=paul@mybboard.net \
/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.