From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: patch against linux-next
Date: Tue, 22 Nov 2016 09:13:19 +0100 [thread overview]
Message-ID: <20161122081319.GB29481@kroah.com> (raw)
In-Reply-To: <1de28614-f5f1-b2d4-1d5f-4e8893965dd9@mrbrklyn.com>
On Tue, Nov 22, 2016 at 12:19:18AM -0500, Ruben Safir wrote:
> On 11/21/2016 11:28 PM, Amit Kumar wrote:
> > On Tue, Nov 22, 2016, 8:41 AM Ruben Safir <ruben@mrbrklyn.com> wrote:
> >
> >> On 11/21/2016 08:48 PM, Amit Kumar wrote:
> >>> Hi,
> >>>
> >>> As far as I know that linux-next tree is a preview of patches which will
> >> be
> >>>
>
> This is an academic area, and has nothing to do with actual kernel
> development. You must know that. Shoot an email off to linus at linux.com
Ruben, you are totally wrong, this is not an "acedemic" area, and that's
a made up linux.com email address. This is the exact type of question
that this mailing list is for.
Please stop.
greg k-h
next prev parent reply other threads:[~2016-11-22 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 1:48 patch against linux-next Amit Kumar
2016-11-22 3:10 ` Ruben Safir
2016-11-22 4:28 ` Amit Kumar
2016-11-22 5:19 ` Ruben Safir
2016-11-22 8:13 ` Greg KH [this message]
2016-11-22 8:14 ` Greg KH
2016-11-22 9:31 ` Amit Kumar
2016-11-22 9:58 ` Greg KH
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=20161122081319.GB29481@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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.