dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
* PSA: drm-misc-next-fixes is open
@ 2023-02-01 10:10 Thomas Zimmermann
  0 siblings, 0 replies; 5+ messages in thread
From: Thomas Zimmermann @ 2023-02-01 10:10 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 1204 bytes --]

Hi,

the email goes out a bit late, as -rc6 has already been tagged for a few 
days. This means that drm-misc-next-fixes is now open for bug fixes, as 
drm-next is in feature freeze until the next -rc1 comes out.

Some rules of thumb on where to land your patch:

    * if your patch fixes a bug in upstream, please put it into 
drm-misc-fixes,

    * if your patch fixes a bug in drm-next, please put it into 
drm-misc-next-fixes,

    * anything else, especially new features, should go into drm-misc-next.

The flow chart is at [1].

The transition from/to drm-misc-fixes-next sometimes results in patches 
that are applied to the wrong tree and get stuck there for a long time. 
If you have fixes in drm-misc-next that must go into drm-next soon, 
please cherry-pick them into drm-misc-next-fixes. We have

    dim cherry-pick

to help you with that.

Best regards
Thomas

[1] 
https://drm.pages.freedesktop.org/maintainer-tools/committer-drm-misc.html#where-do-i-apply-my-patch

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* PSA: drm-misc-next-fixes is open
@ 2023-08-15 12:53 Thomas Zimmermann
  0 siblings, 0 replies; 5+ messages in thread
From: Thomas Zimmermann @ 2023-08-15 12:53 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 1209 bytes --]

Hi,

-rc6 has been tagged for a few days. This means that drm-misc-next-fixes 
is now open for bug fixes, as drm-next is in feature freeze until the 
next -rc1 comes out.

Some rules of thumb on where to land your patch:

      * if your patch fixes a bug in upstream, please put it into 
drm-misc-fixes,

      * if your patch fixes a bug in drm-next, please put it into 
drm-misc-next-fixes,

      * anything else, especially new features, should go into 
drm-misc-next.

The flow chart is at [1].

The transition from/to drm-misc-fixes-next sometimes results in patches 
that are applied to the wrong tree and get stuck there for a long time. 
If you have fixes in drm-misc-next that must go into drm-next soon, 
please cherry-pick them into drm-misc-next-fixes. We have

      dim cherry-pick

to help you with that.

Best regards
Thomas

[1] 
https://drm.pages.freedesktop.org/maintainer-tools/committer-drm-misc.html#where-do-i-apply-my-patch

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* PSA: drm-misc-next-fixes is open
@ 2023-06-15  8:42 Thomas Zimmermann
  0 siblings, 0 replies; 5+ messages in thread
From: Thomas Zimmermann @ 2023-06-15  8:42 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 1166 bytes --]

Hi,

-rc6 has been tagged for a few days. This means that drm-misc-next-fixes 
is now open for bug fixes, as drm-next is in feature freeze until the 
next -rc1 comes out.

Some rules of thumb on where to land your patch:

     * if your patch fixes a bug in upstream, please put it into 
drm-misc-fixes,

     * if your patch fixes a bug in drm-next, please put it into 
drm-misc-next-fixes,

     * anything else, especially new features, should go into drm-misc-next.

The flow chart is at [1].

The transition from/to drm-misc-fixes-next sometimes results in patches 
that are applied to the wrong tree and get stuck there for a long time. 
If you have fixes in drm-misc-next that must go into drm-next soon, 
please cherry-pick them into drm-misc-next-fixes. We have

     dim cherry-pick

to help you with that.

Best regards
Thomas

[1] 
https://drm.pages.freedesktop.org/maintainer-tools/committer-drm-misc.html#where-do-i-apply-my-patch

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* PSA: drm-misc-next-fixes is open
@ 2022-07-14  8:38 Thomas Zimmermann
  0 siblings, 0 replies; 5+ messages in thread
From: Thomas Zimmermann @ 2022-07-14  8:38 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 1146 bytes --]

Hi,

the email goes out a bit late, as -rc6 has already been tagged for a few 
days. This means that drm-misc-next-fixes is now open for bug fixes, as 
drm-next is in feature freeze until the next -rc1 comes out.

Some rules of thumb:

   * if your patch fixes a bug in upstream, please put it into 
drm-misc-fixes,

   * if your patch fixes a bug in drm-next, please put it into 
drm-misc-next-fixes,

   * anything else should go into drm-misc-next.

The flow chart is at [1].

The transition from/to drm-misc-fixes-next sometimes results in patches 
that are applied to the wrong tree and get stuck there for a long time. 
If you have fixes in drm-misc-next that must go into drm-next soon, 
please cherry-pick them into drm-misc-next-fixes. We have

   dim cherry-pick

to help you with that.

Best regards
Thomas

[1] 
https://drm.pages.freedesktop.org/maintainer-tools/committer-drm-misc.html#where-do-i-apply-my-patch

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* PSA: drm-misc-next-fixes is open
@ 2021-12-17 11:23 Thomas Zimmermann
  0 siblings, 0 replies; 5+ messages in thread
From: Thomas Zimmermann @ 2021-12-17 11:23 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 955 bytes --]

Hi,

I'm just letting you know that drm-misc-next-fixes is now open for bug 
fixes. -rc6 will presumably be tagged this weekend, which means that 
drm-next is in feature freeze until the next -rc1 comes out.

The transition from/to drm-misc-fixes-next often results in patches that 
are applied to the wrong tree and get stuck there for a long time. Some 
rules of thumb:

  * if your patch fixes a bug in drm-next, please put it into 
drm-misc-next-fixes,

  * if your patch fixes a bug in upstream, please put it into 
drm-misc-fixes,

  * anything else should go into drm-misc-next.

The flow chart is at [1].

Best regards
Thomas

[1] 
https://drm.pages.freedesktop.org/maintainer-tools/committer-drm-misc.html#where-do-i-apply-my-patch

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2023-08-15 12:53 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-01 10:10 PSA: drm-misc-next-fixes is open Thomas Zimmermann
  -- strict thread matches above, loose matches on Subject: below --
2023-08-15 12:53 Thomas Zimmermann
2023-06-15  8:42 Thomas Zimmermann
2022-07-14  8:38 Thomas Zimmermann
2021-12-17 11:23 Thomas Zimmermann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).