All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Stefan Roese <sr@denx.de>
Cc: "Marek Behún" <kabel@kernel.org>,
	u-boot@lists.denx.de, "Marek Behún" <marek.behun@nic.cz>
Subject: Re: [PATCH u-boot-marvell v2] arm: mvebu: turris_omnia: Fixup SATA or PCIe nodes at runtime in DT blob
Date: Mon, 10 Jan 2022 10:06:25 +0100	[thread overview]
Message-ID: <20220110090625.i2nive52tufw6jx4@pali> (raw)
In-Reply-To: <cca2efc0-aac9-1976-ae90-639cdcb4aa4b@denx.de>

On Monday 10 January 2022 08:43:17 Stefan Roese wrote:
> > +	/* If mSATA card is not present, disable SATA DT node */
> > +	if (!mode_sata) {
> > +		fdt_for_each_node_by_compatible (node, blob, -1,
> > +						 "marvell,armada-380-ahci") {
> 
> Why are adding the space before the "(" here? This does not seem the
> common and preferred coding style AFAICT.

Hello Stefan! Just to note that I'm adding this space too when writing
for-loops. E.g.:

for (i = 0; i < 10; i++) {
...
}

or:

fdt_for_each_node_by_compatible (node, blob, -1, compatible) {
...
}

> > +			if (!fdtdec_get_is_enabled(blob, node))
> > +				continue;
> > +
> > +			if (fdt_status_disabled(blob, node) < 0)
> > +				printf("Cannot disable SATA DT node!\n");
> > +			else
> > +				debug("Disabled SATA DT node\n");
> > +
> > +			break;
> > +		}
> > +
> > +		return;
> > +	}

  reply	other threads:[~2022-01-10  9:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 12:53 [PATCH u-boot-marvell v2] arm: mvebu: turris_omnia: Fixup SATA or PCIe nodes at runtime in DT blob Marek Behún
2022-01-10  7:43 ` Stefan Roese
2022-01-10  9:06   ` Pali Rohár [this message]
2022-01-10  9:10     ` Stefan Roese
2022-01-10 10:47 Marek Behún
2022-01-13  7:20 ` Stefan Roese
2022-01-20 16:19 ` Stefan Roese

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=20220110090625.i2nive52tufw6jx4@pali \
    --to=pali@kernel.org \
    --cc=kabel@kernel.org \
    --cc=marek.behun@nic.cz \
    --cc=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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.