From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: query: omap-defconfigs
Date: Wed, 12 Aug 2009 07:35:41 -0700 [thread overview]
Message-ID: <87iqgt14n6.fsf@deeprootsystems.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608702F598989C@dbde02.ent.ti.com> (Vikram Pandita's message of "Wed\, 12 Aug 2009 03\:01\:37 +0530")
"Pandita, Vikram" <vikram.pandita@ti.com> writes:
> For the omap board defconfigs, is there a plan to remove these entries:
> CONFIG_SYSFS_DEPRECATED=y
> CONFIG_SYSFS_DEPRECATED_V2=y
>
> I can see that on pm branch on kevin's tree, these are not enabled.
>
> With older busybox, I needed these entries to be enabled, but switching to latest busybox 1_9_2 I could disable these entries without problem.
>
> Anything we would break by removing these DEPRECATED entries?
I vote to remove them since using OE or OE-based distros like Arago
require them to be disabled.
Kevin
next prev parent reply other threads:[~2009-08-12 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 21:31 query: omap-defconfigs Pandita, Vikram
2009-08-12 14:35 ` Kevin Hilman [this message]
2009-08-12 14:39 ` Pandita, Vikram
2009-08-12 20:07 ` Koen Kooi
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=87iqgt14n6.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=vikram.pandita@ti.com \
/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