From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Peter Hurley <peter@hurleysoftware.com>,
Jiri Slaby <jslaby@suse.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Jiri Slaby <jslaby@suse.cz>,
Andrey Konovalov <andreyknvl@google.com>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Hans Boehm <hboehm@google.com>
Subject: Re: [PATCH] tty: fix data race in tty_buffer_flush
Date: Thu, 17 Sep 2015 05:51:55 -0700 [thread overview]
Message-ID: <20150917125155.GA16085@kroah.com> (raw)
In-Reply-To: <CACT4Y+a8VW4KKMBpZSy0Vo22JRocNQW_259JxGERLEKTWjbrBA@mail.gmail.com>
On Thu, Sep 17, 2015 at 12:28:11PM +0200, Dmitry Vyukov wrote:
> One stupid question. There is a number of branches:
> remotes/origin/master
> remotes/origin/tty-linus
> remotes/origin/tty-next
> remotes/origin/tty-testing
>
> What branch should I base my patches on? I used master.
Right now, if you look, they all point to the same thing, so it doesn't
matter :)
tty-linus is for patches to go to Linus this kernel release.
tty-next is for patches to go to Linus the next kernel release.
Both tty-linus and tty-next show up in linux-next and are never rebased.
tty-testing is for patches that are being considered for tty-next, it
does not show up in linux-next and sometimes is rebased if things go
wrong with the patches.
Hope this helps,
greg k-h
prev parent reply other threads:[~2015-09-17 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 12:26 Dmitry Vyukov
2015-09-08 12:48 ` Dmitry Vyukov
2015-09-08 22:11 ` Greg KH
2015-09-16 1:38 ` Peter Hurley
2015-09-16 18:20 ` Dmitry Vyukov
2015-09-17 10:28 ` Dmitry Vyukov
2015-09-17 10:59 ` Dmitry Vyukov
2015-09-17 12:51 ` Greg Kroah-Hartman [this message]
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=20150917125155.GA16085@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hboehm@google.com \
--cc=jslaby@suse.com \
--cc=jslaby@suse.cz \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peter@hurleysoftware.com \
/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
Powered by JetHome