From: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Frank Rowand <frowand.list@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
devel@driverdev.osuosl.org
Subject: Re: [RFC 0/2] Juniper DT based connector driver
Date: Sat, 8 Oct 2016 19:11:54 +0300 [thread overview]
Message-ID: <45F613B3-5666-40E2-9D77-E8A536503DAA@konsulko.com> (raw)
In-Reply-To: <CAL_Jsq+eMNw0Q9ZWx1UV8YrBgzVfB+O6gDjwTU9kvwwbKp+vmA@mail.gmail.com>
Hi Rob,
> On Oct 8, 2016, at 19:10 , Rob Herring <robh+dt@kernel.org> wrote:
>
> On Fri, Oct 7, 2016 at 10:16 AM, Pantelis Antoniou
> <pantelis.antoniou@konsulko.com> 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.
>
> Because you haven't sent them out again. There were only minor issues.
> Someone else said recently they were going to refresh them, but I
> haven't seen them.
>
Yes, they will go out right after ELCE.
> Rob
Regards
— Pantelis
prev parent reply other threads:[~2016-10-08 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 15:16 [RFC 0/2] Juniper DT based connector driver 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 ` [RFC 0/2] Juniper DT based connector driver Greg Kroah-Hartman
2016-10-08 16:10 ` Rob Herring
2016-10-08 16:11 ` Pantelis Antoniou [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=45F613B3-5666-40E2-9D77-E8A536503DAA@konsulko.com \
--to=pantelis.antoniou@konsulko.com \
--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=gregkh@linuxfoundation.org \
--cc=gvlaev@juniper.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.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;
as well as URLs for NNTP newsgroup(s).