public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Philippe REYNES <philippe.reynes@softathome.com>
Cc: u-boot@lists.denx.de, anand.gore@broadcom.com,
	william.zhang@broadcom.com, kursad.oney@broadcom.com,
	joel.peshkin@broadcom.com
Subject: Re: [PATCH] drivers: led: bcm6858: do not use null label to find the top
Date: Wed, 19 Jul 2023 09:06:22 -0400	[thread overview]
Message-ID: <20230719130622.GT1670569@bill-the-cat> (raw)
In-Reply-To: <aebe8589-641f-b625-f98c-cb7665fc4aba@softathome.com>

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

On Wed, Jul 19, 2023 at 02:13:06PM +0200, Philippe REYNES wrote:
> Hi Tom,
> 
> 
> Le 18/07/2023 à 15:43, Tom Rini a écrit :
> > On Tue, Jul 18, 2023 at 11:20:52AM +0200, Philippe REYNES wrote:
> > > Hi Tom,
> > > 
> > > For this patch, I see that it is accepted on patchwork:
> > > https://patchwork.ozlabs.org/project/uboot/patch/20230623163642.241034-1-philippe.reynes@softathome.com/
> > > But I don't see it in master/next.
> > > 
> > > Is it a "miss" or I have to update it please ?
> > This commit:
> > https://source.denx.de/u-boot/u-boot/-/commit/910b01c27c0499ae8f84104a0db745dd3a056c04
> > 
> > is that patch, yes?
> 
> 
> No, it is not this patch
> 
> I have sent two patches:
> 
> one for bcm6753:
> https://patchwork.ozlabs.org/project/uboot/patch/20230629092523.448644-1-philippe.reynes@softathome.com/
> => I see it in the branch master: https://source.denx.de/u-boot/u-boot/-/commit/910b01c27c0499ae8f84104a0db745dd3a056c04
> 
> one for 6858:
> https://patchwork.ozlabs.org/project/uboot/patch/20230623163642.241034-1-philippe.reynes@softathome.com/
> => I don't see this patch in the branch master
> 
> 
> Note:  there are still some others led driver that are broken:
> - bcm6328
> - bcm6358
> - cortina

I missed the numbers, sorry, thanks for clarifying.  I've moved this
back to New in patchwork and I'm not sure why it was in Accepted.

-- 
Tom

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

  reply	other threads:[~2023-07-19 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 16:36 [PATCH] drivers: led: bcm6858: do not use null label to find the top Philippe Reynes
2023-07-18  9:20 ` Philippe REYNES
2023-07-18 13:43   ` Tom Rini
2023-07-19 12:13     ` Philippe REYNES
2023-07-19 13:06       ` Tom Rini [this message]
2023-07-25 21:12 ` Tom Rini

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=20230719130622.GT1670569@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=anand.gore@broadcom.com \
    --cc=joel.peshkin@broadcom.com \
    --cc=kursad.oney@broadcom.com \
    --cc=philippe.reynes@softathome.com \
    --cc=u-boot@lists.denx.de \
    --cc=william.zhang@broadcom.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