From: "Jörn Engel" <joern@logfs.org>
To: Brian Norris <computersforpeace@gmail.com>
Cc: "Jussi Kivilinna" <jussi.kivilinna@iki.fi>,
linux-usb@vger.kernel.org,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"David Woodhouse" <dwmw2@infradead.org>,
"Bjørn Mork" <bjorn@mork.no>
Subject: Re: [PATCH] alauda: do not use stack for URB transfer_buffers
Date: Wed, 21 Aug 2013 15:06:05 -0400 [thread overview]
Message-ID: <20130821190604.GA14552@logfs.org> (raw)
In-Reply-To: <CAN8TOE9Ed=2YgV7L7gHB7FZC8OyE9=vr=6rVUQDPoK54NHh3ZA@mail.gmail.com>
On Wed, 21 August 2013 13:00:15 -0700, Brian Norris wrote:
>
> Yes, that's a good point. Quoting Documentation/stable_kernel_rules.txt:
>
> "It must be obviously correct and tested."
>
> Seeing as it was not tested, I am dropping the patch entirely (it is
> not stable material, and there is no point including it along with the
> driver removal).
Thank you! Without quoting rules, this also fails the common sense
test. For a stable patch, one might assume a non-empty group of
people that would benefit from said patch and care enough to install
the patch.
Jörn
--
I have always found the word "Europe" in the mouth of those politicians
that were demanding something from other powers they did not dare demand
in their own name.
-- Otto von Bismarck
prev parent reply other threads:[~2013-08-21 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 12:03 [PATCH] alauda: do not use stack for URB transfer_buffers Jussi Kivilinna
2013-08-06 16:49 ` Jörn Engel
2013-08-07 5:50 ` Jussi Kivilinna
2013-08-07 15:16 ` Jörn Engel
2013-08-21 7:30 ` Brian Norris
2013-08-21 7:59 ` Bjørn Mork
2013-08-21 8:41 ` Brian Norris
2013-08-21 9:59 ` Jussi Kivilinna
2013-08-21 20:00 ` Brian Norris
2013-08-21 19:06 ` Jörn Engel [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=20130821190604.GA14552@logfs.org \
--to=joern@logfs.org \
--cc=bjorn@mork.no \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jussi.kivilinna@iki.fi \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-usb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.