linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ilya Zykov <ilya@ilyx.ru>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, Jiri Slaby <jslaby@suse.cz>
Subject: Re: [PATCH v2] TTY: pty, fix pty counting in "/proc/sys/kernel/pty/nr"
Date: Thu, 27 Oct 2011 17:41:36 +0400	[thread overview]
Message-ID: <4EA95F90.6000107@ilyx.ru> (raw)
In-Reply-To: <20111027123742.GB7910@kroah.com>

Greg KH wrote:

> On Thu, Oct 27, 2011 at 01:48:35PM +0400, Ilya Zykov wrote:
>> Regression for commit: 24d406a6bf736f7aebdc8fa0f0ec86e0890c6d24
>> Commit: 24d406a6b accepted in Linux 3.1.
>> Disscussed on linux-kernel@vger.kernel.org "subject: [PATCH] TTY: pty, fix pty counting"
>> and not accepted.
>> Although, I think it's clear.
> 
> Ilya, is there some reason you are ignoring the tty maintainer and
> sending these to Linus directly?  These patches need to be tested in
> linux-next, so at the earliest, they can be merged into Linus's tree for
> 3.3, they are NOT 3.2 material, especially given that they are not even
> accepted by the current tty developers.
> 
> So please work with us, and don't try to circumvent the existing
> process, it is not the way we work here.
> 
> Especially as this specific patch was already rejected, for very good
> reasons, why are you ignoring those reasons?
> 
> thanks,
> 
> greg k-h
> 


But I don't understand, what for, "pty" driver, calling tty_driver_remove_tty(), 
only for call its own function(pty_unix98_remove).


Thank you.
Ilya.


      parent reply	other threads:[~2011-10-27 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27  9:48 [PATCH v2] TTY: pty, fix pty counting in "/proc/sys/kernel/pty/nr" Ilya Zykov
2011-10-27 12:37 ` Greg KH
2011-10-27 13:07   ` Ilya Zykov
2011-10-27 15:01     ` Greg KH
2011-10-27 13:41   ` Ilya Zykov [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=4EA95F90.6000107@ilyx.ru \
    --to=ilya@ilyx.ru \
    --cc=greg@kroah.com \
    --cc=jslaby@suse.cz \
    --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).