All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Sullivan <nathan.sullivan@ni.com>
To: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>
Cc: <ralf@linux-mips.org>, <mark.rutland@arm.com>,
	<robh+dt@kernel.org>, <linux-mips@linux-mips.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MIPS: NI 169445 board support
Date: Fri, 2 Dec 2016 11:30:20 -0600	[thread overview]
Message-ID: <20161202173020.GA22514@nathan3500-linux-VM> (raw)
In-Reply-To: <04fd3008-14b1-b5e1-1895-093f0076644d@imgtec.com>

On Fri, Dec 02, 2016 at 04:21:59PM +0000, Zubair Lutfullah Kakakhel wrote:
> Hi,
> 
> On 12/02/2016 03:42 PM, Nathan Sullivan wrote:
> >Support the National Instruments 169445 board.
> 
> Interesting patch.
> 
> But do you happen to have a link to a description of the board?
> I couldn't find anything with a quick search.
> Perhaps the public name is something else?
> 
> Thanks,
> ZubairLK

This patch is for a pre-release board we have not made public yet.  It's a
straightforward MIPS system that will be used for networking, and we'd like to
get Linux support in place ahead of release.

Thanks,
Nathan

WARNING: multiple messages have this Message-ID (diff)
From: Nathan Sullivan <nathan.sullivan@ni.com>
To: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>
Cc: ralf@linux-mips.org, mark.rutland@arm.com, robh+dt@kernel.org,
	linux-mips@linux-mips.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: NI 169445 board support
Date: Fri, 2 Dec 2016 11:30:20 -0600	[thread overview]
Message-ID: <20161202173020.GA22514@nathan3500-linux-VM> (raw)
Message-ID: <20161202173020.TAt_qziWlkUOnilHX_ZTP4Hp5eimiVrujtk2vIn0oiA@z> (raw)
In-Reply-To: <04fd3008-14b1-b5e1-1895-093f0076644d@imgtec.com>

On Fri, Dec 02, 2016 at 04:21:59PM +0000, Zubair Lutfullah Kakakhel wrote:
> Hi,
> 
> On 12/02/2016 03:42 PM, Nathan Sullivan wrote:
> >Support the National Instruments 169445 board.
> 
> Interesting patch.
> 
> But do you happen to have a link to a description of the board?
> I couldn't find anything with a quick search.
> Perhaps the public name is something else?
> 
> Thanks,
> ZubairLK

This patch is for a pre-release board we have not made public yet.  It's a
straightforward MIPS system that will be used for networking, and we'd like to
get Linux support in place ahead of release.

Thanks,
Nathan

  reply	other threads:[~2016-12-02 17:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 15:42 [PATCH] MIPS: NI 169445 board support Nathan Sullivan
2016-12-02 15:42 ` Nathan Sullivan
2016-12-02 16:21 ` Zubair Lutfullah Kakakhel
2016-12-02 16:21   ` Zubair Lutfullah Kakakhel
2016-12-02 17:30   ` Nathan Sullivan [this message]
2016-12-02 17:30     ` Nathan Sullivan
2016-12-09 21:18 ` Rob Herring
2016-12-09 21:18   ` Rob Herring
2016-12-14 16:32   ` Nathan Sullivan
2016-12-14 16:32     ` Nathan Sullivan
2016-12-14 16:32     ` Nathan Sullivan
2016-12-14 16:48     ` Rob Herring
2016-12-13 18:40 ` Paul Burton
2016-12-13 18:40   ` Paul Burton
2016-12-13 18:40   ` Paul Burton
2016-12-13 18:56   ` Nathan Sullivan
2016-12-13 18:56     ` Nathan Sullivan
2016-12-13 18:56     ` Nathan Sullivan
     [not found] ` <20161220163434.GA15962@linux-mips.org>
2017-01-04 16:38   ` Nathan Sullivan
2017-01-04 16:38     ` Nathan Sullivan
2017-01-05 18:28     ` Niklas Cassel
2017-01-05 18:28       ` Niklas Cassel
2017-01-05 18:33       ` Joao Pinto
2017-01-05 18:33         ` Joao Pinto
2017-01-05 18:44         ` Nathan Sullivan
2017-01-05 18:44           ` Nathan Sullivan
2017-01-05 18:45           ` Joao Pinto
2017-01-05 18:45             ` Joao Pinto
  -- strict thread matches above, loose matches on Subject: below --
2017-07-14 17:16 RESEND PATCH v5 Nathan Sullivan
2017-07-14 17:16 ` [PATCH] MIPS: NI 169445 board support Nathan Sullivan
2017-07-14 17:16   ` Nathan Sullivan

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=20161202173020.GA22514@nathan3500-linux-VM \
    --to=nathan.sullivan@ni.com \
    --cc=Zubair.Kakakhel@imgtec.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mark.rutland@arm.com \
    --cc=ralf@linux-mips.org \
    --cc=robh+dt@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 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.