Displaying 4 results from an estimated 4 matches for "_improves_".
2023 Jul 13
2
[Freedreno] [PATCH RFC v1 00/52] drm/crtc: Rename struct drm_crtc::dev to drm_dev
...n argument which the
kernel as a wider entity typically accepts? If not could it be a
slippery slope to start a precedent?
It is a honest question - I am not familiar if there were or were not
any similar discussions in the past.
My gut feeling is that *if* there is a consensus that something
_improves_ the code base significantly, backporting pains should
probably not be weighted very heavily as a contra argument.
Regards,
Tvrtko
2023 Jul 13
2
[Freedreno] [PATCH RFC v1 00/52] drm/crtc: Rename struct drm_crtc::dev to drm_dev
...n argument which the
kernel as a wider entity typically accepts? If not could it be a
slippery slope to start a precedent?
It is a honest question - I am not familiar if there were or were not
any similar discussions in the past.
My gut feeling is that *if* there is a consensus that something
_improves_ the code base significantly, backporting pains should
probably not be weighted very heavily as a contra argument.
Regards,
Tvrtko
2023 Jul 13
1
[Freedreno] [PATCH RFC v1 00/52] drm/crtc: Rename struct drm_crtc::dev to drm_dev
On Thu, Jul 13, 2023 at 9:04?AM Uwe Kleine-K?nig
<u.kleine-koenig at pengutronix.de> wrote:
>
> hello Sean,
>
> On Wed, Jul 12, 2023 at 02:31:02PM -0400, Sean Paul wrote:
> > I'd really prefer this patch (series or single) is not accepted. This
> > will cause problems for everyone cherry-picking patches to a
> > downstream kernel (LTS or distro tree). I
2023 Jul 13
1
[Freedreno] [PATCH RFC v1 00/52] drm/crtc: Rename struct drm_crtc::dev to drm_dev
On Thu, Jul 13, 2023 at 9:04?AM Uwe Kleine-K?nig
<u.kleine-koenig at pengutronix.de> wrote:
>
> hello Sean,
>
> On Wed, Jul 12, 2023 at 02:31:02PM -0400, Sean Paul wrote:
> > I'd really prefer this patch (series or single) is not accepted. This
> > will cause problems for everyone cherry-picking patches to a
> > downstream kernel (LTS or distro tree). I