Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-31 Thread Simon Glass
Hi Troy, On Mon, 30 Jan 2023 at 15:17, Troy Kisky wrote: > > > > On Mon, Jan 30, 2023 at 11:44 AM Tom Rini wrote: >> >> On Mon, Jan 30, 2023 at 10:51:03AM -0800, Troy Kisky wrote: >> > Hi Tom >> > >> > >> > On Mon, Jan 30, 2023 at 9:18 AM Tom Rini wrote: >> > >> > > On Sat, Jan 28, 2023 at 09:2

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-30 Thread Troy Kisky
On Mon, Jan 30, 2023 at 11:44 AM Tom Rini wrote: > On Mon, Jan 30, 2023 at 10:51:03AM -0800, Troy Kisky wrote: > > Hi Tom > > > > > > On Mon, Jan 30, 2023 at 9:18 AM Tom Rini wrote: > > > > > On Sat, Jan 28, 2023 at 09:25:54AM -0800, Troy Kisky wrote: > > > > Thanks Tom, > > > > > > > > I cleane

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-30 Thread Tom Rini
On Mon, Jan 30, 2023 at 10:51:03AM -0800, Troy Kisky wrote: > Hi Tom > > > On Mon, Jan 30, 2023 at 9:18 AM Tom Rini wrote: > > > On Sat, Jan 28, 2023 at 09:25:54AM -0800, Troy Kisky wrote: > > > Thanks Tom, > > > > > > I cleaned up the PR based on the CI results. Here's my current changes. > >

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-30 Thread Troy Kisky
Hi Tom On Mon, Jan 30, 2023 at 9:18 AM Tom Rini wrote: > On Sat, Jan 28, 2023 at 09:25:54AM -0800, Troy Kisky wrote: > > Thanks Tom, > > > > I cleaned up the PR based on the CI results. Here's my current changes. > > > > Author: Troy Kisky > > Date: Fri Jan 27 11:03:11 2023 -0800 > > > >

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-30 Thread Tom Rini
On Sat, Jan 28, 2023 at 09:25:54AM -0800, Troy Kisky wrote: > Thanks Tom, > > I cleaned up the PR based on the CI results. Here's my current changes. > > Author: Troy Kisky > Date: Fri Jan 27 11:03:11 2023 -0800 > > dm: device-internal: use EVENT instead of DM_EVENT, because > event_notif

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-28 Thread Troy Kisky
Thanks Tom, I cleaned up the PR based on the CI results. Here's my current changes. Author: Troy Kisky Date: Fri Jan 27 11:03:11 2023 -0800 dm: device-internal: use EVENT instead of DM_EVENT, because event_notify is built for EVENT Signed-off-by: Troy Kisky diff --git a/include/dm/

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-27 Thread Simon Glass
Hi Tom, On Thu, 26 Jan 2023 at 14:33, Tom Rini wrote: > > On Thu, Jan 26, 2023 at 02:29:53PM -0700, Simon Glass wrote: > > Hi Tom, > > > > On Thu, 26 Jan 2023 at 11:16, Tom Rini wrote: > > > > > > On Thu, Jan 26, 2023 at 11:04:21AM -0700, Simon Glass wrote: > > > > Hi Tom, > > > > > > > > On Thu

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-26 Thread Tom Rini
On Thu, Jan 26, 2023 at 02:29:53PM -0700, Simon Glass wrote: > Hi Tom, > > On Thu, 26 Jan 2023 at 11:16, Tom Rini wrote: > > > > On Thu, Jan 26, 2023 at 11:04:21AM -0700, Simon Glass wrote: > > > Hi Tom, > > > > > > On Thu, 26 Jan 2023 at 10:21, Tom Rini wrote: > > > > > > > > On Tue, Jan 24, 20

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-26 Thread Simon Glass
Hi Tom, On Thu, 26 Jan 2023 at 11:16, Tom Rini wrote: > > On Thu, Jan 26, 2023 at 11:04:21AM -0700, Simon Glass wrote: > > Hi Tom, > > > > On Thu, 26 Jan 2023 at 10:21, Tom Rini wrote: > > > > > > On Tue, Jan 24, 2023 at 06:36:00PM -0700, Simon Glass wrote: > > > > Hi Troy, > > > > > > > > On Tu

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-26 Thread Tom Rini
On Thu, Jan 26, 2023 at 11:04:21AM -0700, Simon Glass wrote: > Hi Tom, > > On Thu, 26 Jan 2023 at 10:21, Tom Rini wrote: > > > > On Tue, Jan 24, 2023 at 06:36:00PM -0700, Simon Glass wrote: > > > Hi Troy, > > > > > > On Tue, 24 Jan 2023 at 16:31, Troy Kisky > > > wrote: > > > > > > > > > > > >

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-26 Thread Simon Glass
Hi Tom, On Thu, 26 Jan 2023 at 10:21, Tom Rini wrote: > > On Tue, Jan 24, 2023 at 06:36:00PM -0700, Simon Glass wrote: > > Hi Troy, > > > > On Tue, 24 Jan 2023 at 16:31, Troy Kisky > > wrote: > > > > > > > > > > > > > > > From: Troy Kisky > > > Sent: Tuesday, Ja

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-26 Thread Tom Rini
On Thu, Jan 26, 2023 at 09:26:18AM -0800, Troy Kisky wrote: > Thanks Simon > > I switched emails to get rid of the legalese. > Below are scripts to commit the changes sorted by > CONFIG_x variable. The only one I know causes a problem > is CONFIG_OF_LIVE because of > > drivers/core/Makefile > obj

re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-26 Thread Troy Kisky
Thanks Simon I switched emails to get rid of the legalese. Below are scripts to commit the changes sorted by CONFIG_x variable. The only one I know causes a problem is CONFIG_OF_LIVE because of drivers/core/Makefile obj-$(CONFIG_$(SPL_)OF_LIVE) So, that config needs to keep using CONFIG_IS_ENABL

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-26 Thread Tom Rini
On Tue, Jan 24, 2023 at 06:36:00PM -0700, Simon Glass wrote: > Hi Troy, > > On Tue, 24 Jan 2023 at 16:31, Troy Kisky wrote: > > > > > > > > > > From: Troy Kisky > > Sent: Tuesday, January 24, 2023 2:52 PM > > To: u-boot@lists.denx.de ; sba...@denx.de > > ; tr...@

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-24 Thread Simon Glass
Hi Troy, On Tue, 24 Jan 2023 at 16:31, Troy Kisky wrote: > > > > > From: Troy Kisky > Sent: Tuesday, January 24, 2023 2:52 PM > To: u-boot@lists.denx.de ; sba...@denx.de > ; tr...@konsulko.com ; feste...@gmail.com > > Cc: s...@chromium.org ; ma...@denx.de > Su

Re: CONFIG_IS_ENABLED vs IS_ENABLED

2023-01-24 Thread Troy Kisky
From: Troy Kisky Sent: Tuesday, January 24, 2023 2:52 PM To: u-boot@lists.denx.de ; sba...@denx.de ; tr...@konsulko.com ; feste...@gmail.com Cc: s...@chromium.org ; ma...@denx.de Subject: CONFIG_IS_ENABLED vs IS_ENABLED Hi Guys In a recent debugging session