From: Anatolij Gustschin <agust@denx.de>
To: "Ondřej Jirman" <megi@xff.cz>
Cc: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>,
Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [PATCH 0/8] Some fixes for the rockchip dw_mipi_dsi driver
Date: Mon, 17 Jul 2023 18:01:47 +0200 [thread overview]
Message-ID: <20230717180147.35139f91@crub> (raw)
In-Reply-To: <kx4x6oy5obewbnoyiktj5b56bz5jhs4emy2hin72ecqlsstyoj@bd24g6sp6erc>
On Thu, 13 Jul 2023 18:03:48 +0200
Ondřej Jirman megi@xff.cz wrote:
> On Thu, Jul 13, 2023 at 05:47:47PM +0200, Anatolij Gustschin wrote:
> >
> > On Thu, 13 Jul 2023 16:51:36 +0200
> > Ondřej Jirman megi@xff.cz wrote:
> >
> > > Hi,
> > >
> > > On Mon, May 22, 2023 at 11:47:00PM +0200, megi xff wrote:
> > > >
> > > >
> > > > From: Ondrej Jirman <megi@xff.cz>
> > > >
> > > > These are just random fixes for bugs I found while eyeballing the code and porting
> > > > it to work with RK3399.
> > >
> > > It would be nice if somebody merged this. I'd like to add display support for
> > > a few boards, and these patches are just fairly obvious bugfixes in new code
> > > added in 2023.07 that I hoped would get merged in the bugfix part of the merge
> > > window.
> >
> > I hoped to get a Tested-by for this series to make sure it does not break
> > current users.
>
> It's a miracle it even works for the current users, given the wrong
> way the current code writes to GRF registers, which makes it to have
> no intended effect, etc.
>
> Anyway, is there some upper limit to wait for Tested-by? 2 months seems
> excessive. Just so I can remind myself sooner next time. :)
>
> I can understand a few weeks, but 2 months just deters contributions.
I usually apply new patches during the merge window (we have three months
release cycle) and this patch series was sent when the merge window was
closed. If patches are bug fixes (like in this case) I prefer to get them
tested by someone who has the actual hardware. When there is an Acked-by
or Tested-by, then I apply the fixes for -rcX. We already had several cases
in the past where simple and obvious timing fixes in the driver broke
display support for in tree boards, therefore I'm somewhat reluctant to
apply fixes for -rcX without Tested-by.
--
Anatolij
next prev parent reply other threads:[~2023-07-17 16:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 21:47 [PATCH 0/8] Some fixes for the rockchip dw_mipi_dsi driver megi
2023-05-22 21:47 ` [PATCH 1/8] video: rockchip: vop: Fix whitespace megi
2023-05-26 0:51 ` Kever Yang
2023-05-22 21:47 ` [PATCH 2/8] video: dw_mipi_dsi: Fix hsync/vsync settings megi
2023-05-22 21:47 ` [PATCH 3/8] video: rockchip: dw_mipi_dsi: Fix external phy existnece check megi
2023-05-22 21:47 ` [PATCH 4/8] video: rockchip: dw_mipi_dsi: Fix error path checks in probe function megi
2023-05-22 21:47 ` [PATCH 5/8] video: rockchip: dw_mipi_dsi: Return 0 from dsi_phy_init on success megi
2023-05-22 21:47 ` [PATCH 6/8] video: rockchip: dw_mipi_dsi: Fix best_rate calculation megi
2023-05-22 21:47 ` [PATCH 7/8] video: rockchip: dw_mipi_dsi: Correct check for lacking phy phandle megi
2023-05-22 21:47 ` [PATCH 8/8] video: rockchip: dw_mipi_dsi: Fix GRF access megi
2023-07-13 14:51 ` [PATCH 0/8] Some fixes for the rockchip dw_mipi_dsi driver Ondřej Jirman
2023-07-13 15:47 ` Anatolij Gustschin
2023-07-13 16:03 ` Ondřej Jirman
2023-07-17 16:01 ` Anatolij Gustschin [this message]
2023-07-17 16:13 ` Ondřej Jirman
2023-07-17 17:20 ` Christopher Morgan
2023-07-17 15:25 ` Anatolij Gustschin
2023-07-25 18:03 ` Chris Morgan
2023-07-25 18:34 ` Ondřej Jirman
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=20230717180147.35139f91@crub \
--to=agust@denx.de \
--cc=kever.yang@rock-chips.com \
--cc=macromorgan@hotmail.com \
--cc=megi@xff.cz \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox