[PATCH 17/23] video: Convert CONFIG_VIDEO_LOGO to Kconfig

[Pali Rohár]

On Sunday 23 January 2022 09:54:02 Tom Rini wrote:
> On Sun, Jan 23, 2022 at 03:48:17PM +0100, Pali Rohár wrote:
> > On Saturday 22 January 2022 13:41:01 Tom Rini wrote:
> > > On Sat, Jan 22, 2022 at 04:41:42PM +0100, Pali Rohár wrote:
> > > > Adding other Maemo developers...
> > > > 
> > > > On Saturday 22 January 2022 10:29:34 Tom Rini wrote:
> > > > > This is perhaps as good/bad time as any to ask about the conversion
> > > > > efforts for N900 USB things that were discussed before?
> > > > 
> > > > Perhaps it is also a good/bad time for reminding that some N900 U-Boot
> > > > patches are waiting for review on the list? :-)
> > > 
> > > The last ones I saw weren't clear what it depended on and should get
> > > re-posted.
> > 
> > And how should I or anybody else know this if nobody is responding to
> > emails asking for review of pending patches?
> 
> I thought the last time you ping'd on it Lokesh was confused about what
> this was on top of / required.

I think I sent info how to apply it. But as I have not received any
reply even after reminding, how should I have know it?

> > > But I didn't see anything about the USB DM conversion.
> > 
> > Of course, as there are waiting other patches and other emails without
> > replies, it is not a wise idea to start working on something other or
> > starting discussion about something totally new if existing things are
> > waiting for maintainers...
> 
> I believe it was someone else that is interested in N900 that said they
> would look at it.

Yea, for USB it was Merlijn. He wrote me that would reply later to this
thread. This thread started about video and not USB, so there is just
big mix of things and I forgot about what we are talking here...

> > I wanted to look at other stuff after pending patches are in accepted
> > state. But I'm not superman to work on 10 parallel things at the same
> > time and specially if I see that reviewing N900 patches is slow and
> > takes about half of year.
> > 
> > If I see that maintainer is busy then I send just one patch and next
> > after it is accepted. And not sending thousands of patches at the same
> > time. If I would be in the "busy maintainer" position I also would not
> > like to see thousands of patches waiting from other developers and
> > rather would see one patch and after it is accepted then another patch.
> > 
> > So, could you please make a time and look at pending N900 patching?
> > So we can move forward? I have feeling that this is repeating every year
> > and the ball is not on my side.
> > 
> > For example I'm still waiting for reply for this email from July 2021:
> > https://lists.denx.de/pipermail/u-boot/2021-July/455710.html
> > 
> > And sending reminder for another patch in December 2021 has no reply too:
> > https://lists.denx.de/pipermail/u-boot/2021-December/468744.html
> 
> My problem is that re-reading those threads again just now leaves me at
> "please re-base and re-post everything because it wasn't clear at all
> what goes where".  My only other feedback is that it would I think be
> better to move and then update the documentation, not improve, migrate,
> improve more.

Ok, so I will resend patches. When would you have a time to review these
patches? I do not want again to repeat situation that I will send a
patch and after half of year I get reply that it does not apply on
master and rebasing is needed. So please let me know when you would have
a time for review of N900 so I would send patches at correct timing
without need from my side to rebase and rebase patches again and
again... because this is really annoying for me and also wasting of time
... and it happened with more N900 patch in last 2 years.