From: Greg KH <gregkh@linuxfoundation.org>
To: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Cc: Sujith Manoharan <c_manoha@qca.qualcomm.com>,
"Balasubramanian, Senthil Kumar" <senthilb@qca.qualcomm.com>,
"Manoharan, Rajkumar" <rmanohar@qca.qualcomm.com>,
qca-linux-team <qca-linux-team@qualcomm.com>,
Imran Ansari <imran@qca.qualcomm.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
sfr@canb.auug.org.au, mcgrof@frijolero.org, hauke@hauke-m.de,
ozancag@gmail.com, pstew@google.com, warthog9@kernel.org,
jrnieder@gmail.com, ben@decadent.org.uk,
akpm@linux-foundation.org, linville@tuxdriver.com
Subject: Re: 3.5 stable compat-wireless
Date: Thu, 5 Jul 2012 16:08:42 -0700 [thread overview]
Message-ID: <20120705230842.GA26510@kroah.com> (raw)
In-Reply-To: <20120705190801.GB11228@tux>
On Thu, Jul 05, 2012 at 12:08:01PM -0700, Luis R. Rodriguez wrote:
> * linux-crap.git: based on linux-next-pending.git and allows
> contributors to send pull requests of crap that is not *ready*
> to be sent properly upstream. Examples would be code we know
> we simply already know that is not dealing with proper architecture
> or style / etc. The drivers/staging/ allows vendors to post full
> crap drivers, this would enable us to merge crap patches but that
> some vendors might need / want.
I really doubt this will work, look at the patches in some distros for
examples of why. I'm having a hard enough time with the LTSI project in
conveying that "Yes, you can send patches to me for merging into the
LSTI kernel, you still have to justify it, and work to get the patches
then upstream, I'm not going to do your work for you."
Having a random tree where these patches show up help no one except the
original developer so that they can fire-and-forget, which is not what
you want, unless you wish to take on the "get it cleaned up and merged
upstream" task yourself, which you really don't want to.
good luck,
greg k-h
next prev parent reply other threads:[~2012-07-05 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20468.35601.132955.802881@gargle.gargle.HOWL>
[not found] ` <7A9ADFFA56024346AAE90B6BABC3BD15DD6DEB@NASANEXD02B.na.qualcomm.com>
[not found] ` <20469.13787.767293.602337@gargle.gargle.HOWL>
2012-07-05 19:08 ` 3.5 stable compat-wireless Luis R. Rodriguez
2012-07-05 23:08 ` Greg KH [this message]
2012-07-05 23:18 ` Luis R. Rodriguez
2012-07-06 1:06 ` Sujith Manoharan
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=20120705230842.GA26510@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=c_manoha@qca.qualcomm.com \
--cc=hauke@hauke-m.de \
--cc=imran@qca.qualcomm.com \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@frijolero.org \
--cc=ozancag@gmail.com \
--cc=pstew@google.com \
--cc=qca-linux-team@qualcomm.com \
--cc=rmanohar@qca.qualcomm.com \
--cc=rodrigue@qca.qualcomm.com \
--cc=senthilb@qca.qualcomm.com \
--cc=sfr@canb.auug.org.au \
--cc=warthog9@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).