All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ARC:  ARC_BOARD_ANGEL4 and ARC_BOARD_ML509
Date: Mon, 22 Sep 2014 05:16:54 +0000	[thread overview]
Message-ID: <C2D7FE5348E1B147BCA15975FBA230753C5DA1BE@IN01WEMBXA.internal.synopsys.com> (raw)
In-Reply-To: 1410512426.31130.11.camel@x220

On Friday 12 September 2014 02:30 PM, Paul Bolle wrote:
> Hi Vineet,
>
> On Mon, 2014-06-09 at 09:05 +0000, Vineet Gupta wrote:
>> On Wednesday 04 June 2014 03:04 PM, Paul Bolle wrote:
>>> Linux-next included commit c00bfd974fb0 ("ARC: [arcfpga] Get rid of
>>> legacy BVCI latency unit support") in next-20140604. It removes the
>>> Kconfig symbol ARC_HAS_BVCI_LAT_UNIT. And that symbol's entry is the
>>> only place were the symbols ARC_BOARD_ANGEL4 and ARC_BOARD_ML509 are
>>> currently used. So it follows that the entries for ARC_BOARD_ANGEL4 and
>>> ARC_BOARD_ML509 could be removed too.
>> Thx for noticing this.
>>
>> I'm planning to use these symbols to set up default builtin DT blobs from Kconfig
>> itself (rather than current defconfigs). If that doesn't workout - sure I will
>> remove the symbols.
> No news here as of v3.17-rc4 and next-20140912. Are you still planning
> to use these symbols or should I submit the trivial patch to drop them?

Please send over patch - I'll queue it up for 3.18

Thx,
-Vineet

>
> Thanks,
>
>
> Paul Bolle
>
>


  reply	other threads:[~2014-09-22  5:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  9:33 ARC: ARC_BOARD_ANGEL4 and ARC_BOARD_ML509 Paul Bolle
2014-06-09  9:05 ` Vineet Gupta
2014-09-12  9:00   ` Paul Bolle
2014-09-22  5:16     ` Vineet Gupta [this message]
2014-09-23  9:39       ` [PATCH] ARC: [arcfpga] Get rid of " Paul Bolle
2014-09-25  7:22         ` Vineet Gupta
2014-09-25  7:58           ` Vineet Gupta

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=C2D7FE5348E1B147BCA15975FBA230753C5DA1BE@IN01WEMBXA.internal.synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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.