netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: rmilasan@suse.com
Cc: jslaby@suse.cz, jasowang@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, jirislaby@gmail.com,
	maxk@qualcomm.com
Subject: Re: "tuntap: multiqueue support" causes udev fork bombs
Date: Wed, 28 Nov 2012 10:25:49 -0500 (EST)	[thread overview]
Message-ID: <20121128.102549.1498532034068614087.davem@davemloft.net> (raw)
In-Reply-To: <20121128113043.39a56f22@coolcat.suse.cz>


Please DO NOT quote a huge email, just to give a small reply to the
discussion.  It is never appropriate.

Doing so wastes bandwidth for every single person on the list.

Just quote enough context, and in the case you really could have
quoted nothing at all and everyone would have understood you.

Thanks.

  reply	other threads:[~2012-11-28 15:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28 10:25 "tuntap: multiqueue support" causes udev fork bombs Jiri Slaby
2012-11-28 10:30 ` Robert Milasan
2012-11-28 15:25   ` David Miller [this message]
2012-11-29  5:47 ` Jason Wang
2012-11-30 17:01   ` 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=20121128.102549.1498532034068614087.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jasowang@redhat.com \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.com \
    --cc=netdev@vger.kernel.org \
    --cc=rmilasan@suse.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).