Message ID | 1eba1bc0-ba0c-b948-6a3d-51a98f4e5c27@gmail.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [pull] ttm drm-fixes-5.4 | expand |
For some reason this didn't end up in patchwork which makes it hard for me to process. Usual suspects are using too old a git to send it or maybe it got ctrl-Ms in it. Dave. On Thu, 3 Oct 2019 at 01:44, Christian König <ckoenig.leichtzumerken@gmail.com> wrote: > > Hi Dave, Daniel, > > we had some problems this cycle sending out TTM fixes because of lack of > time to rebase amd-staging-drm-next. > > Because of this Alex and I decided that I'm going to send out TTM pull > requests separately now. So this is the first small bunch of fixes for 5.4. > > The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c: > > Linux 5.4-rc1 (2019-09-30 10:35:40 -0700) > > are available in the Git repository at: > > https://gitlab.freedesktop.org/ckoenig/linux-drm.git drm-ttm-fixes > > for you to fetch changes up to 3eefcfe9a644be4409691b44c3b2d629d177fb9a: > > drm/ttm: Restore ttm prefaulting (2019-10-02 15:57:34 +0200) > > ---------------------------------------------------------------- > Christian König (1): > drm/ttm: fix busy reference in ttm_mem_evict_first > > Thomas Hellstrom (1): > drm/ttm: Restore ttm prefaulting > > drivers/gpu/drm/ttm/ttm_bo.c | 4 ++-- > drivers/gpu/drm/ttm/ttm_bo_vm.c | 16 +++++++--------- > 2 files changed, 9 insertions(+), 11 deletions(-) > > Regards, > Christian.
My git version should be relative new, but I'm usually using thunderbird to send pull requests not git itself since I want to edit the message before sending. How would I do this in a way patchwork likes it with git? Thanks, Christian. Am 07.10.19 um 21:58 schrieb Dave Airlie: > For some reason this didn't end up in patchwork which makes it hard > for me to process. > > Usual suspects are using too old a git to send it or maybe it got ctrl-Ms in it. > > Dave. > > On Thu, 3 Oct 2019 at 01:44, Christian König > <ckoenig.leichtzumerken@gmail.com> wrote: >> Hi Dave, Daniel, >> >> we had some problems this cycle sending out TTM fixes because of lack of >> time to rebase amd-staging-drm-next. >> >> Because of this Alex and I decided that I'm going to send out TTM pull >> requests separately now. So this is the first small bunch of fixes for 5.4. >> >> The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c: >> >> Linux 5.4-rc1 (2019-09-30 10:35:40 -0700) >> >> are available in the Git repository at: >> >> https://gitlab.freedesktop.org/ckoenig/linux-drm.git drm-ttm-fixes >> >> for you to fetch changes up to 3eefcfe9a644be4409691b44c3b2d629d177fb9a: >> >> drm/ttm: Restore ttm prefaulting (2019-10-02 15:57:34 +0200) >> >> ---------------------------------------------------------------- >> Christian König (1): >> drm/ttm: fix busy reference in ttm_mem_evict_first >> >> Thomas Hellstrom (1): >> drm/ttm: Restore ttm prefaulting >> >> drivers/gpu/drm/ttm/ttm_bo.c | 4 ++-- >> drivers/gpu/drm/ttm/ttm_bo_vm.c | 16 +++++++--------- >> 2 files changed, 9 insertions(+), 11 deletions(-) >> >> Regards, >> Christian.
On Tue, Oct 8, 2019 at 4:04 AM Koenig, Christian <Christian.Koenig@amd.com> wrote: > > My git version should be relative new, but I'm usually using thunderbird > to send pull requests not git itself since I want to edit the message > before sending. > > How would I do this in a way patchwork likes it with git? FWIW, I usually generate the email first and then use git-send-email to actually send it. Alex > > Thanks, > Christian. > > Am 07.10.19 um 21:58 schrieb Dave Airlie: > > For some reason this didn't end up in patchwork which makes it hard > > for me to process. > > > > Usual suspects are using too old a git to send it or maybe it got ctrl-Ms in it. > > > > Dave. > > > > On Thu, 3 Oct 2019 at 01:44, Christian König > > <ckoenig.leichtzumerken@gmail.com> wrote: > >> Hi Dave, Daniel, > >> > >> we had some problems this cycle sending out TTM fixes because of lack of > >> time to rebase amd-staging-drm-next. > >> > >> Because of this Alex and I decided that I'm going to send out TTM pull > >> requests separately now. So this is the first small bunch of fixes for 5.4. > >> > >> The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c: > >> > >> Linux 5.4-rc1 (2019-09-30 10:35:40 -0700) > >> > >> are available in the Git repository at: > >> > >> https://gitlab.freedesktop.org/ckoenig/linux-drm.git drm-ttm-fixes > >> > >> for you to fetch changes up to 3eefcfe9a644be4409691b44c3b2d629d177fb9a: > >> > >> drm/ttm: Restore ttm prefaulting (2019-10-02 15:57:34 +0200) > >> > >> ---------------------------------------------------------------- > >> Christian König (1): > >> drm/ttm: fix busy reference in ttm_mem_evict_first > >> > >> Thomas Hellstrom (1): > >> drm/ttm: Restore ttm prefaulting > >> > >> drivers/gpu/drm/ttm/ttm_bo.c | 4 ++-- > >> drivers/gpu/drm/ttm/ttm_bo_vm.c | 16 +++++++--------- > >> 2 files changed, 9 insertions(+), 11 deletions(-) > >> > >> Regards, > >> Christian. > > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel
On Tue, Oct 08, 2019 at 09:13:41AM -0400, Alex Deucher wrote: > On Tue, Oct 8, 2019 at 4:04 AM Koenig, Christian > <Christian.Koenig@amd.com> wrote: > > > > My git version should be relative new, but I'm usually using thunderbird > > to send pull requests not git itself since I want to edit the message > > before sending. > > > > How would I do this in a way patchwork likes it with git? > > FWIW, I usually generate the email first and then use git-send-email > to actually send it. > > Alex Hey, FDO patchwork maintainer here. I have tried few things quickly with no luck. There is something fishy about FDO deployment of patchwork - you email works just fine on my development instance. I have created issue for this: https://gitlab.freedesktop.org/patchwork-fdo/patchwork-fdo/issues/28 Sorry for the inconvenience. Cheers, Arek > > Thanks, > > Christian. > > > > Am 07.10.19 um 21:58 schrieb Dave Airlie: > > > For some reason this didn't end up in patchwork which makes it hard > > > for me to process. > > > > > > Usual suspects are using too old a git to send it or maybe it got ctrl-Ms in it. > > > > > > Dave. > > > > > > On Thu, 3 Oct 2019 at 01:44, Christian König > > > <ckoenig.leichtzumerken@gmail.com> wrote: > > >> Hi Dave, Daniel, > > >> > > >> we had some problems this cycle sending out TTM fixes because of lack of > > >> time to rebase amd-staging-drm-next. > > >> > > >> Because of this Alex and I decided that I'm going to send out TTM pull > > >> requests separately now. So this is the first small bunch of fixes for 5.4. > > >> > > >> The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c: > > >> > > >> Linux 5.4-rc1 (2019-09-30 10:35:40 -0700) > > >> > > >> are available in the Git repository at: > > >> > > >> https://gitlab.freedesktop.org/ckoenig/linux-drm.git drm-ttm-fixes > > >> > > >> for you to fetch changes up to 3eefcfe9a644be4409691b44c3b2d629d177fb9a: > > >> > > >> drm/ttm: Restore ttm prefaulting (2019-10-02 15:57:34 +0200) > > >> > > >> ---------------------------------------------------------------- > > >> Christian König (1): > > >> drm/ttm: fix busy reference in ttm_mem_evict_first > > >> > > >> Thomas Hellstrom (1): > > >> drm/ttm: Restore ttm prefaulting > > >> > > >> drivers/gpu/drm/ttm/ttm_bo.c | 4 ++-- > > >> drivers/gpu/drm/ttm/ttm_bo_vm.c | 16 +++++++--------- > > >> 2 files changed, 9 insertions(+), 11 deletions(-) > > >> > > >> Regards, > > >> Christian. > > > > _______________________________________________ > > dri-devel mailing list > > dri-devel@lists.freedesktop.org > > https://lists.freedesktop.org/mailman/listinfo/dri-devel > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel
Am 09.10.19 um 09:47 schrieb Arkadiusz Hiler: > On Tue, Oct 08, 2019 at 09:13:41AM -0400, Alex Deucher wrote: >> On Tue, Oct 8, 2019 at 4:04 AM Koenig, Christian >> <Christian.Koenig@amd.com> wrote: >>> My git version should be relative new, but I'm usually using thunderbird >>> to send pull requests not git itself since I want to edit the message >>> before sending. >>> >>> How would I do this in a way patchwork likes it with git? >> FWIW, I usually generate the email first and then use git-send-email >> to actually send it. >> >> Alex > Hey, > > FDO patchwork maintainer here. > > I have tried few things quickly with no luck. There is something fishy > about FDO deployment of patchwork - you email works just fine on my > development instance. > > I have created issue for this: > https://gitlab.freedesktop.org/patchwork-fdo/patchwork-fdo/issues/28 > > Sorry for the inconvenience. Maybe it's the non-Latin letter in my last name? Anyway we need to get the TTM fixes upstream for 5.4. Dave/Daniel any objections that I push those directly to drm-misc-fixes? Thanks, Christian. > > Cheers, > Arek > >>> Thanks, >>> Christian. >>> >>> Am 07.10.19 um 21:58 schrieb Dave Airlie: >>>> For some reason this didn't end up in patchwork which makes it hard >>>> for me to process. >>>> >>>> Usual suspects are using too old a git to send it or maybe it got ctrl-Ms in it. >>>> >>>> Dave. >>>> >>>> On Thu, 3 Oct 2019 at 01:44, Christian König >>>> <ckoenig.leichtzumerken@gmail.com> wrote: >>>>> Hi Dave, Daniel, >>>>> >>>>> we had some problems this cycle sending out TTM fixes because of lack of >>>>> time to rebase amd-staging-drm-next. >>>>> >>>>> Because of this Alex and I decided that I'm going to send out TTM pull >>>>> requests separately now. So this is the first small bunch of fixes for 5.4. >>>>> >>>>> The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c: >>>>> >>>>> Linux 5.4-rc1 (2019-09-30 10:35:40 -0700) >>>>> >>>>> are available in the Git repository at: >>>>> >>>>> https://gitlab.freedesktop.org/ckoenig/linux-drm.git drm-ttm-fixes >>>>> >>>>> for you to fetch changes up to 3eefcfe9a644be4409691b44c3b2d629d177fb9a: >>>>> >>>>> drm/ttm: Restore ttm prefaulting (2019-10-02 15:57:34 +0200) >>>>> >>>>> ---------------------------------------------------------------- >>>>> Christian König (1): >>>>> drm/ttm: fix busy reference in ttm_mem_evict_first >>>>> >>>>> Thomas Hellstrom (1): >>>>> drm/ttm: Restore ttm prefaulting >>>>> >>>>> drivers/gpu/drm/ttm/ttm_bo.c | 4 ++-- >>>>> drivers/gpu/drm/ttm/ttm_bo_vm.c | 16 +++++++--------- >>>>> 2 files changed, 9 insertions(+), 11 deletions(-) >>>>> >>>>> Regards, >>>>> Christian. >>> _______________________________________________ >>> dri-devel mailing list >>> dri-devel@lists.freedesktop.org >>> https://lists.freedesktop.org/mailman/listinfo/dri-devel >> _______________________________________________ >> dri-devel mailing list >> dri-devel@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/dri-devel
On Thu, 10 Oct 2019 at 21:58, Koenig, Christian <Christian.Koenig@amd.com> wrote: > > Am 09.10.19 um 09:47 schrieb Arkadiusz Hiler: > > On Tue, Oct 08, 2019 at 09:13:41AM -0400, Alex Deucher wrote: > >> On Tue, Oct 8, 2019 at 4:04 AM Koenig, Christian > >> <Christian.Koenig@amd.com> wrote: > >>> My git version should be relative new, but I'm usually using thunderbird > >>> to send pull requests not git itself since I want to edit the message > >>> before sending. > >>> > >>> How would I do this in a way patchwork likes it with git? > >> FWIW, I usually generate the email first and then use git-send-email > >> to actually send it. > >> > >> Alex > > Hey, > > > > FDO patchwork maintainer here. > > > > I have tried few things quickly with no luck. There is something fishy > > about FDO deployment of patchwork - you email works just fine on my > > development instance. > > > > I have created issue for this: > > https://gitlab.freedesktop.org/patchwork-fdo/patchwork-fdo/issues/28 > > > > Sorry for the inconvenience. > > Maybe it's the non-Latin letter in my last name? Anyway we need to get > the TTM fixes upstream for 5.4. > > Dave/Daniel any objections that I push those directly to drm-misc-fixes? Don't bother, I can manually process it, just takes a bit more effort. Dave.
On Fri, 11 Oct 2019 at 14:20, Dave Airlie <airlied@gmail.com> wrote: > > On Thu, 10 Oct 2019 at 21:58, Koenig, Christian > <Christian.Koenig@amd.com> wrote: > > > > Am 09.10.19 um 09:47 schrieb Arkadiusz Hiler: > > > On Tue, Oct 08, 2019 at 09:13:41AM -0400, Alex Deucher wrote: > > >> On Tue, Oct 8, 2019 at 4:04 AM Koenig, Christian > > >> <Christian.Koenig@amd.com> wrote: > > >>> My git version should be relative new, but I'm usually using thunderbird > > >>> to send pull requests not git itself since I want to edit the message > > >>> before sending. > > >>> > > >>> How would I do this in a way patchwork likes it with git? > > >> FWIW, I usually generate the email first and then use git-send-email > > >> to actually send it. > > >> > > >> Alex > > > Hey, > > > > > > FDO patchwork maintainer here. > > > > > > I have tried few things quickly with no luck. There is something fishy > > > about FDO deployment of patchwork - you email works just fine on my > > > development instance. > > > > > > I have created issue for this: > > > https://gitlab.freedesktop.org/patchwork-fdo/patchwork-fdo/issues/28 > > > > > > Sorry for the inconvenience. > > > > Maybe it's the non-Latin letter in my last name? Anyway we need to get > > the TTM fixes upstream for 5.4. > > > > Dave/Daniel any objections that I push those directly to drm-misc-fixes? > > Don't bother, I can manually process it, just takes a bit more effort. Actually it has a problem, you need to Signed-off-by any commits you touch. The first patch should to be correect have your Sob after Thomas review as you touched it last, the second patch needs your Sob somewhere in it. Dave.
On Fri, Oct 11, 2019 at 6:24 AM Dave Airlie <airlied@gmail.com> wrote: > > On Fri, 11 Oct 2019 at 14:20, Dave Airlie <airlied@gmail.com> wrote: > > > > On Thu, 10 Oct 2019 at 21:58, Koenig, Christian > > <Christian.Koenig@amd.com> wrote: > > > > > > Am 09.10.19 um 09:47 schrieb Arkadiusz Hiler: > > > > On Tue, Oct 08, 2019 at 09:13:41AM -0400, Alex Deucher wrote: > > > >> On Tue, Oct 8, 2019 at 4:04 AM Koenig, Christian > > > >> <Christian.Koenig@amd.com> wrote: > > > >>> My git version should be relative new, but I'm usually using thunderbird > > > >>> to send pull requests not git itself since I want to edit the message > > > >>> before sending. > > > >>> > > > >>> How would I do this in a way patchwork likes it with git? > > > >> FWIW, I usually generate the email first and then use git-send-email > > > >> to actually send it. > > > >> > > > >> Alex > > > > Hey, > > > > > > > > FDO patchwork maintainer here. > > > > > > > > I have tried few things quickly with no luck. There is something fishy > > > > about FDO deployment of patchwork - you email works just fine on my > > > > development instance. > > > > > > > > I have created issue for this: > > > > https://gitlab.freedesktop.org/patchwork-fdo/patchwork-fdo/issues/28 > > > > > > > > Sorry for the inconvenience. > > > > > > Maybe it's the non-Latin letter in my last name? Anyway we need to get > > > the TTM fixes upstream for 5.4. > > > > > > Dave/Daniel any objections that I push those directly to drm-misc-fixes? > > > > Don't bother, I can manually process it, just takes a bit more effort. > > Actually it has a problem, you need to Signed-off-by any commits you touch. > > The first patch should to be correect have your Sob after Thomas > review as you touched it last, > the second patch needs your Sob somewhere in it. So yeah maybe -misc because that makes sure this is all correct :-) -Daniel