[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191021171104.GY5610@atomide.com>
Date: Mon, 21 Oct 2019 10:11:04 -0700
From: Tony Lindgren <tony@...mide.com>
To: "H. Nikolaus Schaller" <hns@...delico.com>
Cc: Mark Rutland <mark.rutland@....com>,
Ulf Hansson <ulf.hansson@...aro.org>,
devicetree@...r.kernel.org, Yangtao Li <tiny.windzz@...il.com>,
linux-wireless@...r.kernel.org,
Kefeng Wang <wangkefeng.wang@...wei.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
letux-kernel@...nphoenux.org,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Russell King <linux@...linux.org.uk>,
Mike Rapoport <rppt@...ux.ibm.com>,
Kalle Valo <kvalo@...eaurora.org>,
Petr Mladek <pmladek@...e.com>,
BenoƮt Cousson <bcousson@...libre.com>,
kernel@...a-handheld.com,
Alexios Zavras <alexios.zavras@...el.com>,
Rob Herring <robh+dt@...nel.org>,
John Stultz <john.stultz@...aro.org>,
David Sterba <dsterba@...e.com>,
Thomas Gleixner <tglx@...utronix.de>,
linux-omap@...r.kernel.org, Allison Randal <allison@...utok.net>,
linux-arm-kernel@...ts.infradead.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
netdev@...r.kernel.org
Subject: Re: [PATCH v2 07/11] omap: remove old hsmmc.[ch] and in Makefile
* H. Nikolaus Schaller <hns@...delico.com> [191021 17:08]:
>
> > Am 21.10.2019 um 16:30 schrieb Tony Lindgren <tony@...mide.com>:
> >
> > * H. Nikolaus Schaller <hns@...delico.com> [191019 18:43]:
> >> --- a/arch/arm/mach-omap2/Makefile
> >> +++ b/arch/arm/mach-omap2/Makefile
> >> @@ -216,7 +216,6 @@ obj-$(CONFIG_MACH_NOKIA_N8X0) += board-n8x0.o
> >>
> >> # Platform specific device init code
> >>
> >> -omap-hsmmc-$(CONFIG_MMC_OMAP_HS) := hsmmc.o
> >> obj-y += $(omap-hsmmc-m) $(omap-hsmmc-y)
> >
> > The related obj-y line can go now too, right?
>
> Yes, I think so. It is a construction that I have never seen before :)
> Therefore I did not recognize that it is related.
>
> > And looks like common.h also has struct omap2_hsmmc_info
> > so maybe check by grepping for hsmmc_info to see it's gone.
>
> Yes, it is just a forward-declaration of the struct name with
> no user anywhere.
>
> Scheduled for v3.
>
> BTW: should this series go through your tree since it is an
> omap machine?
Or MMC tree as that's where the code change really are.
Regards,
Tony
Powered by blists - more mailing lists