From: Alan Cox <alan@linux.intel.com>
To: Florian Fainelli <ffainelli@freebox.fr>
Cc: linux-kernel@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>,
"Gustavo F. Padovan" <padovan@profusion.mobi>,
Wolfgang Grandegger <wg@grandegger.com>,
Andreas Koensgen <ajk@comnets.uni-bremen.de>,
Samuel Ortiz <samuel@sortiz.org>,
Paul Mackerras <paulus@samba.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Mikael Starvik <starvik@axis.com>,
Jesper Nilsson <jesper.nilsson@axis.com>,
Pavan Savoy <pavan_savoy@ti.com>, Felipe Balbi <balbi@ti.com>,
Thomas Gleixner <tglx@linutronix.de>,
David Miller <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>,
Oliver Hartkopp <socketcan@hartkopp.net>,
Tobias Klauser <tklauser@distanz.ch>, Jiri Slaby <jslaby@suse.cz>,
linux-bluetooth@vger.kernel.org, socketcan-core@lists.berlios.de,
netdev@vger.kernel.org, linux-hams@vger.kernel.org,
linux-ppp@vger.kernel.org, linux-cris-kernel@axis.com,
linux-serial@vger.kernel.org
Subject: Re: [PATCH] TTY: define TTY_MAX_RECEIVE_ROOM to 65536
Date: Tue, 14 Jun 2011 14:24:46 +0100 [thread overview]
Message-ID: <20110614142446.063c0859@bob.linux.org.uk> (raw)
In-Reply-To: <1308057986-11472-1-git-send-email-ffainelli@freebox.fr>
On Tue, 14 Jun 2011 15:26:25 +0200
Florian Fainelli <ffainelli@freebox.fr> wrote:
> A lot of TTY drivers are setting their receive_room value to 65536
> so let's define a constant for this.
These are not all the same thing so NAK
Linus wants to get rid of tty->receive_room anyway
prev parent reply other threads:[~2011-06-14 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 13:26 [PATCH] TTY: define TTY_MAX_RECEIVE_ROOM to 65536 Florian Fainelli
2011-06-14 13:24 ` Alan Cox [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=20110614142446.063c0859@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=ajk@comnets.uni-bremen.de \
--cc=balbi@ti.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=ffainelli@freebox.fr \
--cc=gregkh@suse.de \
--cc=jesper.nilsson@axis.com \
--cc=jslaby@suse.cz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-cris-kernel@axis.com \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=padovan@profusion.mobi \
--cc=paulus@samba.org \
--cc=pavan_savoy@ti.com \
--cc=samuel@sortiz.org \
--cc=socketcan-core@lists.berlios.de \
--cc=socketcan@hartkopp.net \
--cc=starvik@axis.com \
--cc=tglx@linutronix.de \
--cc=tklauser@distanz.ch \
--cc=wg@grandegger.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;
as well as URLs for NNTP newsgroup(s).