From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Cc: Debjit Ghosh <dghosh@juniper.net>,
Georgi Vlaev <gvlaev@juniper.net>,
Guenter Roeck <linux@roeck-us.net>,
Mohammad Kamil <mkamil@juniper.net>,
Rajat Jain <rajatjain@juniper.net>,
Shyamshankar Dharmarajan <shyamd@juniper.net>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH 0/2] Juniper infrastructure
Date: Fri, 7 Oct 2016 17:28:48 +0200 [thread overview]
Message-ID: <20161007152848.GA10482@kroah.com> (raw)
In-Reply-To: <1475853346-21890-1-git-send-email-pantelis.antoniou@konsulko.com>
On Fri, Oct 07, 2016 at 06:15:44PM +0300, Pantelis Antoniou wrote:
> Introduce a staging driver containing all the bit and
> pieces of Juniper's board support infrastructure that don't quite
> fit in any other place.
Why staging?
> The Juniper series of routers comprise of both x86 and powerpc
> platforms that contain similar hardware components necessitating
> common support methods.
>
> Note that this is the first submission and we expect things to be
> moved around as required.
>
> This patchset is against mainline as of today: v4.8-9431-g3477d16
> and is dependent on the "Juniper prerequisites" patchset sent
> earlier.
sent where? Why not just make a single patch series?
> Rajat Jain (1):
> jnx: Introduce include/linux/jnx/pci_ids.h
>
> Tom Kavanagh (1):
> staging: jnx: Juniper subsystem & board core APIs
>
> Documentation/ABI/testing/sysfs-platform-jnx | 170 +++++++
> drivers/staging/Kconfig | 2 +
> drivers/staging/Makefile | 1 +
> drivers/staging/jnx/Kconfig | 24 +
> drivers/staging/jnx/Makefile | 5 +
> drivers/staging/jnx/jnx-board-core.c | 247 ++++++++++
> drivers/staging/jnx/jnx-subsys-private.h | 35 ++
> drivers/staging/jnx/jnx-subsys.c | 655 +++++++++++++++++++++++++++
> include/linux/jnx/jnx-board-core.h | 41 ++
> include/linux/jnx/jnx-subsys.h | 94 ++++
> include/linux/jnx/pci_ids.h | 66 +++
staging drivers have to be self-contained, no files outside of your
subdirectory please.
Once they have "passed" proper review, then you can move files out.
Also, I need a TODO file listing what needs to be done, who to contact,
and other info about the code.
And again, why not just submit this to the real part of the kernel?
thanks,
greg k-h
prev parent reply other threads:[~2016-10-07 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 15:15 [PATCH 0/2] Juniper infrastructure Pantelis Antoniou
2016-10-07 15:15 ` [PATCH 1/2] staging: jnx: Juniper subsystem & board core APIs Pantelis Antoniou
2016-10-07 15:34 ` Greg Kroah-Hartman
2016-10-07 15:15 ` [PATCH 2/2] jnx: Introduce include/linux/jnx/pci_ids.h Pantelis Antoniou
2016-10-07 15:31 ` Greg Kroah-Hartman
2016-10-07 15:28 ` Greg Kroah-Hartman [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=20161007152848.GA10482@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=dghosh@juniper.net \
--cc=gvlaev@juniper.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mkamil@juniper.net \
--cc=pantelis.antoniou@konsulko.com \
--cc=rajatjain@juniper.net \
--cc=shyamd@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 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.