mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Frank Rowand <frowand.list@gmail.com>,
	Alon Ronen <aronen@juniper.net>,
	Debjit Ghosh <dghosh@juniper.net>,
	Dhruva Diveneni <ddevineni@juniper.net>,
	Georgi Vlaev <gvlaev@juniper.net>,
	Guenter Roeck <linux@roeck-us.net>, Yu-Lin Lu <ylu@juniper.net>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	devel@driverdev.osuosl.org
Subject: Re: [RFC 0/2] Juniper DT based connector driver
Date: Fri, 7 Oct 2016 17:30:14 +0200	[thread overview]
Message-ID: <20161007153014.GC10482@kroah.com> (raw)
In-Reply-To: <1475853372-21997-1-git-send-email-pantelis.antoniou@konsulko.com>

On Fri, Oct 07, 2016 at 06:16:10PM +0300, Pantelis Antoniou wrote:
> Introduce a Juniper PTX router series DT overlay based
> connector driver.
> 
> This is submitted as an RFC since some OF infrastructure
> patches (like changeset helpers etc) are not yet mainlined.

staging drivers almost always need to at least build (or if not, have a
good reason why not.)

So don't post code until people can at least test-build it, otherwise no
one will care about it.  Would you review such code?

thanks,

greg k-h

  parent reply	other threads:[~2016-10-07 15:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 15:16 Pantelis Antoniou
2016-10-07 15:16 ` [RFC 1/2] staging: jnx: Add Juniper " Pantelis Antoniou
2016-10-07 16:25   ` Joe Perches
2016-10-07 18:57     ` Pantelis Antoniou
2016-10-07 15:16 ` [RFC 2/2] staging: jnx-connector: add device tree binding Pantelis Antoniou
2016-10-08 16:05   ` Rob Herring
2016-10-07 15:30 ` Greg Kroah-Hartman [this message]
2016-10-08 16:10 ` [RFC 0/2] Juniper DT based connector driver Rob Herring
2016-10-08 16:11   ` Pantelis Antoniou

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=20161007153014.GC10482@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aronen@juniper.net \
    --cc=ddevineni@juniper.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dghosh@juniper.net \
    --cc=frowand.list@gmail.com \
    --cc=gvlaev@juniper.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mark.rutland@arm.com \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=robh+dt@kernel.org \
    --cc=ylu@juniper.net \
    /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
Powered by JetHome