public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Dave Gerlach <d-gerlach@ti.com>, Lukasz Majewski <lukma@denx.de>,
	Sean Anderson <seanga2@gmail.com>, Peng Fan <peng.fan@nxp.com>,
	Jaehoon Chung <jh80.chung@samsung.com>,
	Simon Glass <sjg@chromium.org>, Suman Anna <s-anna@ti.com>,
	Nishanth Menon <nm@ti.com>,
	Aswath Govindraju <a-govindraju@ti.com>,
	Bryan Brattlof <bb@ti.com>,
	u-boot@lists.denx.de, Georgi Vlaev <g-vlaev@ti.com>
Subject: Re: [PATCH 04/11] arm: mach-k3: Introduce the basic files to support AM62
Date: Fri, 15 Apr 2022 13:41:51 -0400	[thread overview]
Message-ID: <20220415174151.GF14282@bill-the-cat> (raw)
In-Reply-To: <671fac45-c933-0a86-6e90-b155608aee85@ti.com>

[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]

On Fri, Apr 15, 2022 at 10:08:32PM +0530, Vignesh Raghavendra wrote:
> 
> 
> On 15/04/22 9:57 pm, Tom Rini wrote:
> > On Fri, Apr 15, 2022 at 07:39:24PM +0530, Vignesh Raghavendra wrote:
> > 
> > [snip]
> >> diff --git a/arch/arm/mach-k3/am625_init.c b/arch/arm/mach-k3/am625_init.c
> >> new file mode 100644
> >> index 0000000000..ee902a774e
> >> --- /dev/null
> >> +++ b/arch/arm/mach-k3/am625_init.c
> >> @@ -0,0 +1,254 @@
> >> +// SPDX-License-Identifier: GPL-2.0
> >> +/*
> >> + * AM625: SoC specific initialization
> >> + *
> >> + * Copyright (C) 2020-2022 Texas Instruments Incorporated - https://www.ti.com/
> >> + *	Suman Anna <s-anna@ti.com>
> >> + */
> >> +
> >> +#include <common.h>
> >> +#include <spl.h>
> >> +#include <asm/io.h>
> >> +#include <asm/arch/hardware.h>
> >> +#include <asm/arch/sysfw-loader.h>
> >> +#include "common.h"
> >> +#include <dm.h>
> >> +#include <dm/uclass-internal.h>
> >> +#include <dm/pinctrl.h>
> > 
> > Er, common.h twice? 
> 
> Second one refers to arch/arm/mach-k3/common.h

OK, lets rename that, and see what info there we can put elsewhere.

> > Please re-check this, and then also drop common.h
> > (here and elsewhere) as it only includes other headers and we should
> > avoid it when possible.  
> 
> Sure, will do.
> 
> > In fact, checkpatch.pl complains about both
> > dm.h and common.h so please address series-wide, thanks.
> > 
> 
> Unfortunately, it doesn't ;(

Ah, right.  It only checks for inside of headers.  But still should be
avoided.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2022-04-15 17:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 14:09 [PATCH 00/11] TI: Add support for AM62 SoC Vignesh Raghavendra
2022-04-15 14:09 ` [PATCH 01/11] drivers: mmc: am654_sdhci: Add new compatible " Vignesh Raghavendra
2022-04-15 14:09 ` [PATCH 02/11] dt-bindings: pinctrl: k3: Introduce pinmux definitions for AM62 Vignesh Raghavendra
2022-04-15 16:27   ` Tom Rini
2022-04-15 16:36     ` Vignesh Raghavendra
2022-04-15 14:09 ` [PATCH 03/11] soc: ti: k3-socinfo: Add entry for AM62X SoC family Vignesh Raghavendra
2022-04-15 21:00   ` Bryan Brattlof
2022-04-15 14:09 ` [PATCH 04/11] arm: mach-k3: Introduce the basic files to support AM62 Vignesh Raghavendra
2022-04-15 16:27   ` Tom Rini
2022-04-15 16:38     ` Vignesh Raghavendra
2022-04-15 17:41       ` Tom Rini [this message]
2022-04-16  6:47         ` Vignesh Raghavendra
2022-04-15 14:09 ` [PATCH 05/11] arm: mach-k3: am62: Introduce autogenerated SoC data Vignesh Raghavendra
2022-04-15 14:09 ` [PATCH 06/11] dma: ti: Add PSIL data for AM62x DMASS Vignesh Raghavendra
2022-04-15 14:09 ` [PATCH 07/11] arm: dts: Introduce base AM62 SoC dtsi files Vignesh Raghavendra
2022-04-15 16:28   ` Tom Rini
2022-04-15 16:40     ` Vignesh Raghavendra
2022-04-15 14:09 ` [PATCH 08/11] board: ti: Introduce the basic files to support AM62 SK board Vignesh Raghavendra
2022-04-15 14:09 ` [PATCH 09/11] arm: dts: Add support for AM62-SK Vignesh Raghavendra
2022-04-15 14:09 ` [PATCH 10/11] configs: Add configs for AM62x SK Vignesh Raghavendra
2022-04-15 14:09 ` [PATCH 11/11] doc: ti: Add readme " Vignesh Raghavendra
2022-04-15 20:15   ` Bryan Brattlof
2022-04-18 14:56   ` Andrew Davis
2022-04-18 18:49     ` Vignesh Raghavendra

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=20220415174151.GF14282@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=a-govindraju@ti.com \
    --cc=bb@ti.com \
    --cc=d-gerlach@ti.com \
    --cc=g-vlaev@ti.com \
    --cc=jh80.chung@samsung.com \
    --cc=lukma@denx.de \
    --cc=nm@ti.com \
    --cc=peng.fan@nxp.com \
    --cc=s-anna@ti.com \
    --cc=seanga2@gmail.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@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