From: Greg KH <gregkh@suse.de>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Jiri Slaby <jslaby@suse.cz>, Greg KH <greg@kroah.com>,
Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 1/4] TTY: serial, fix locking imbalance
Date: Mon, 26 Sep 2011 16:36:59 -0700 [thread overview]
Message-ID: <20110926233659.GA22611@suse.de> (raw)
In-Reply-To: <4E7E187B.4060507@gmail.com>
On Sat, Sep 24, 2011 at 07:50:51PM +0200, Jiri Slaby wrote:
> On 09/24/2011 12:04 AM, Greg KH wrote:
> > On Fri, Sep 23, 2011 at 09:21:20PM +0200, Jiri Slaby wrote:
> >> But if there are more trees depending on the tree, then OK, I will live
> >> with that ;).
> >
> > For the tty tree, I really doubt it, but I am not sure (rumor has it
> > that some people are basing on it, but that might just be rumor.)
>
> Ok, for the other uart patches I have, it would be convenient for me to
> have the possibility of rebase. Would you mind if I add something like
> uart-cleanup tree to the -next tree and will have the patches there
> until I send them to you?
linux-next is for stuff that people are confident will show up in the
next release, not for general "let's throw it out there to see if it
works" type thing.
> Just for the purpose of fine tuning (and rebasing) if something needs to
> be fixed in them. The code is so complex, that I'm afraid I omitted some
> semi-hidden dependency. And it would be great to fix patches like when I
> used to work with the -mm tree.
Perhaps you should just work with Andrew and put these in -mm for now
until you feel comfortable that it's all worked out and no rebasing
would be needed anymore?
thanks,
greg k-h
next prev parent reply other threads:[~2011-09-26 23:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 19:24 [PATCH 1/4] TTY: serial, fix locking imbalance Jiri Slaby
2011-08-31 19:24 ` [PATCH 2/4] TTY: serial, remove dead code from 68328 Jiri Slaby
2011-08-31 19:51 ` Geert Uytterhoeven
2011-08-31 19:51 ` Geert Uytterhoeven
2011-08-31 19:24 ` [PATCH 3/4] TTY: serial, fix build of some drivers Jiri Slaby
2011-08-31 21:28 ` Alan Cox
2011-09-01 8:29 ` Jiri Slaby
2011-09-01 14:20 ` [PATCH v2 3/4] TTY: serial, fix includes in " Jiri Slaby
2011-08-31 19:24 ` [PATCH 4/4] TTY: serial, move 68360 driver to staging Jiri Slaby
2011-08-31 19:31 ` Sasha Levin
2011-08-31 19:37 ` [PATCH "find-renames version" " Jiri Slaby
2011-08-31 19:41 ` [PATCH " Greg KH
2011-08-31 19:52 ` Geert Uytterhoeven
2011-09-22 18:30 ` [PATCH 1/4] TTY: serial, fix locking imbalance Jiri Slaby
2011-09-22 18:38 ` Greg KH
2011-09-22 22:46 ` Greg KH
2011-09-23 18:52 ` Jiri Slaby
2011-09-23 19:08 ` Greg KH
2011-09-23 19:21 ` Jiri Slaby
2011-09-23 22:04 ` Greg KH
2011-09-24 17:50 ` Jiri Slaby
2011-09-26 23:36 ` Greg KH [this message]
2011-09-27 8:26 ` Jiri Slaby
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=20110926233659.GA22611@suse.de \
--to=gregkh@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nobuhiro.iwamatsu.yj@renesas.com \
--cc=sfr@canb.auug.org.au \
/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).