All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: openbmc@lists.ozlabs.org, Joel Stanley <joel@jms.id.au>,
	Peter Yin <peteryin.openbmc@gmail.com>
Subject: Re: [PATCH u-boot, v2019.04-aspeed-openbmc v1 1/1] ARM: dts: Aspeed: Add Facebook common dts
Date: Fri, 17 May 2024 11:00:08 +0930	[thread overview]
Message-ID: <d1437d773ea682e85cd9f7197453e466ac362fb7.camel@codeconstruct.com.au> (raw)
In-Reply-To: <ZkawtsDBMGT-rTJx@heinlein.vulture-banana.ts.net>

On Thu, 2024-05-16 at 20:19 -0500, Patrick Williams wrote:
> 
> I don't currently have a lot of faith that if we sent a trivial "add the
> new compatible" that it would be accepted in a timely manner.

Well, I'm responding to the patch because I intend to help you get it
merged. I'm trying to keep on top of the patches people send these
days. Can we give it a chance?

> 
> > > 
> > > Should we do something like "facebook,ast2600-standard"?
> > > 
> > 
> > I guess I'm trying to guard-rail the discussion from the position of
> > the compatible strings should be documented in the DT schemas. Is this
> > something that would pass review upstream?
> 
> I don't know?  We're so far removed from upstream at this point that I
> see that as aspirational.  (Everyone using AST2600 is using u-boot
> 2019.04, which was 5 years ago.)

Sure, the tree is not in good shape. However, that doesn't mean we
should go adding fuel to the fire?

> 
> Having said all this, I would love to do things as "right" as possible
> while still being able to make progress.  What is the right step?
> 

That's what I'm trying to figure out in this discussion :) Currently my
thought is "better to keep things concrete and describe actual
platforms", rather than "make up a name for something that vaguely
exists only in principle". I asked about upstream because that allows
you to escape my thoughts and drive the patch through on someone else's
acceptance of your proposal :)

Andrew

  reply	other threads:[~2024-05-17  1:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 14:49 [PATCH u-boot, v2019.04-aspeed-openbmc v1 1/1] ARM: dts: Aspeed: Add Facebook common dts Peter Yin
2024-05-13 23:52 ` Andrew Jeffery
2024-05-15  9:41   ` Peter Yin
2024-05-16  1:00     ` Andrew Jeffery
2024-05-16  2:37       ` Patrick Williams
2024-05-16 23:36         ` Andrew Jeffery
2024-05-17  1:19           ` Patrick Williams
2024-05-17  1:30             ` Andrew Jeffery [this message]
2024-05-17  1:59               ` Patrick Williams

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=d1437d773ea682e85cd9f7197453e466ac362fb7.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    --cc=peteryin.openbmc@gmail.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 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.