From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1B173C433EF for ; Sun, 23 Jan 2022 16:14:28 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id EB2FA8326F; Sun, 23 Jan 2022 17:14:26 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=none (p=none dis=none) header.from=konsulko.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (1024-bit key; unprotected) header.d=konsulko.com header.i=@konsulko.com header.b="p+9K7vlV"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 3C5528326F; Sun, 23 Jan 2022 17:14:25 +0100 (CET) Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 8AD0E81DD0 for ; Sun, 23 Jan 2022 17:14:21 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=none (p=none dis=none) header.from=konsulko.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=trini@konsulko.com Received: by mail-qt1-x831.google.com with SMTP id c15so4056467qtv.1 for ; Sun, 23 Jan 2022 08:14:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=konsulko.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=/82gWlpgyoY+ZqFlReJ798G3gaeNtxraMeWWZ8EZh/s=; b=p+9K7vlVdMoPy2OfxsDrYSS1lf1A/ZhOt4IiBdSL2B70MWoBTo2F928qhAlL0QVVB0 0GlW05su4vpZNKk8SNO2odZc08cA/HR4wJfiK7bOPB7esVTaw8tc4YSsHmJJiHeQlB68 r9JdyKtdjVtpQWYae7bDEYCNg7+ZCWPV8kH9M= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=/82gWlpgyoY+ZqFlReJ798G3gaeNtxraMeWWZ8EZh/s=; b=DL6n1VTXi06WEhRhNCpARaFvu8bnzQ3iLziZHAlCjqhOAG/SY2a3njNwEEBexCRTA2 eAukJJrTqNbuPz7ZKvF4ahovhqHJTjvq3hcuj6E2DdiHqXraeHpNYiniCjRYhGztUu2M hAA2kxCodDaxeIMLcswZXv/bcR/WQxQVLXGN6lpiAjx9hJcRM155a6fkehLw3g9anoFW h0oVICmOROes6NOsHHG2+B/1EkTTKiJgB0BcMJla9wJa1WxsUw211Yt0SXB3t2dCuLKr kWq7klK1fwz51v2WagulG/ImU4OAWgOTnWbO4QnsVDtXsEsIga/uWcQIZly/nBkF/K6y A86g== X-Gm-Message-State: AOAM532kgMV236GCbFNqwGzqhTjMBElNHpTMqs9Hgc3KMRhy4yspXUHL yIJ8l7/kIjwf6Z5R+1DHpQJYag== X-Google-Smtp-Source: ABdhPJzUZhSefDwDfgJ8YFYn87IRnnDte9WuTD4G/Wsiq/AEBOUpp7DNRR7antPWwSmdnIm71xZ1Tg== X-Received: by 2002:a05:622a:548:: with SMTP id m8mr10032314qtx.300.1642954460379; Sun, 23 Jan 2022 08:14:20 -0800 (PST) Received: from bill-the-cat (2603-6081-7b01-cbda-2ef0-5dff-fedb-a8ba.res6.spectrum.com. [2603:6081:7b01:cbda:2ef0:5dff:fedb:a8ba]) by smtp.gmail.com with ESMTPSA id b184sm6236228qkf.87.2022.01.23.08.14.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 23 Jan 2022 08:14:19 -0800 (PST) Date: Sun, 23 Jan 2022 11:14:17 -0500 From: Tom Rini To: Pali =?iso-8859-1?Q?Roh=E1r?= Cc: Merlijn Wajer , maemo-leste@lists.dyne.org, Ivaylo Dimitrov , Simon Glass , U-Boot Mailing List , Anatolij Gustschin , Marek =?iso-8859-1?Q?Beh=FAn?= , Stefan Roese , Stefano Babic Subject: Re: [PATCH 17/23] video: Convert CONFIG_VIDEO_LOGO to Kconfig Message-ID: <20220123161417.GF7515@bill-the-cat> References: <20211119202408.1815506-1-sjg@chromium.org> <20211119202408.1815506-18-sjg@chromium.org> <20220122132611.schnplwxozqzd7ys@pali> <20220122152934.GQ7004@bill-the-cat> <20220122154141.hrj7skg45nnhdh2b@pali> <20220122184101.GS7004@bill-the-cat> <20220123144817.jahhrqz5gx42gn2v@pali> <20220123145402.GA7515@bill-the-cat> <20220123151100.uxyi3g3aw44qm6vu@pali> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="+jhVVhN62yS6hEJ8" Content-Disposition: inline In-Reply-To: <20220123151100.uxyi3g3aw44qm6vu@pali> X-Clacks-Overhead: GNU Terry Pratchett X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.5 at phobos.denx.de X-Virus-Status: Clean --+jhVVhN62yS6hEJ8 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 23, 2022 at 04:11:00PM +0100, Pali Roh=E1r wrote: > On Sunday 23 January 2022 09:54:02 Tom Rini wrote: > > On Sun, Jan 23, 2022 at 03:48:17PM +0100, Pali Roh=E1r wrote: > > > On Saturday 22 January 2022 13:41:01 Tom Rini wrote: > > > > On Sat, Jan 22, 2022 at 04:41:42PM +0100, Pali Roh=E1r wrote: > > > > > Adding other Maemo developers... > > > > >=20 > > > > > On Saturday 22 January 2022 10:29:34 Tom Rini wrote: > > > > > > This is perhaps as good/bad time as any to ask about the conver= sion > > > > > > efforts for N900 USB things that were discussed before? > > > > >=20 > > > > > Perhaps it is also a good/bad time for reminding that some N900 U= -Boot > > > > > patches are waiting for review on the list? :-) > > > >=20 > > > > The last ones I saw weren't clear what it depended on and should get > > > > re-posted. > > >=20 > > > And how should I or anybody else know this if nobody is responding to > > > emails asking for review of pending patches? > >=20 > > I thought the last time you ping'd on it Lokesh was confused about what > > this was on top of / required. >=20 > 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? Other people re-base and re-post, or ping more often. > > > > But I didn't see anything about the USB DM conversion. > > >=20 > > > 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... > >=20 > > I believe it was someone else that is interested in N900 that said they > > would look at it. >=20 > 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... Thanks. > > > 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. > > >=20 > > > 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 patc= h. > > >=20 > > > 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 y= ear > > > and the ball is not on my side. > > >=20 > > > 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 > > >=20 > > > And sending reminder for another patch in December 2021 has no reply = too: > > > https://lists.denx.de/pipermail/u-boot/2021-December/468744.html > >=20 > > 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. >=20 > 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. Documentation patches will go to Heinrich and so long as "make htmldocs" passes, likely be picked up in short order. In general, yes, things will get picked up in the usual cadence of U-Boot release cycles. These particular patches got stuck because of unclear / non-obvious apply order and also Lokesh having been a bit overloaded (I suspect). --=20 Tom --+jhVVhN62yS6hEJ8 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAABCgAdFiEEGjx/cOCPqxcHgJu/FHw5/5Y0tywFAmHtftkACgkQFHw5/5Y0 tyy9hAv/c1IAJQjCBt/zuobRYsBU9zvLpTzTJeV1s47TCHdOZNOR6tr7vpNaFS8+ FpOFIScL8peLw4OqsiBi5dkNyJMV8eQDhGGE4EvNfwxYsO+bl89bKrgUtuLz2JLW v4mkbxkuYSTTeZrFGqeryXpkMuLE9wtIPbFsmL9fB7RS7ewG++So41KROESdb/LM /O4BaD+d9fPI8q4pOl9tpZG6rGsTUyFOFbRtKSt9fkv/UlwGCwl48HMNXyOoDm0k ZnVm7hdWXzNNEyFSHsy8dtiW+USpy9odibB/190r+io0OSqJKCoHQzfiXVAuBjDG zMbaPmJ7hPcabX7nktAVFqs1tXIxWf7RYwrqCh3sJTHtkMkFfF3xByg3NAeunGvH fnH5KS7ZCNhfgAQTJuK+xMSG0E5/BnOhZc4BeZSwz9gvFXaTQ4Svj3NBuBZBtgij JHgHO02NXkaPtypKbe3eVSCYSekJ8zlDeAizOg/ArBnqEiMl7abQlQz1OPOzGLLv VVNdXVR6 =qr3S -----END PGP SIGNATURE----- --+jhVVhN62yS6hEJ8--