All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: russianneuromancer@ya.ru,
	ML dri-devel <dri-devel@lists.freedesktop.org>,
	"# 3.13+" <stable@vger.kernel.org>,
	"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Thierry Reding <treding@nvidia.com>,
	Ikey Doherty <ikey@solus-project.com>,
	Ben Skeggs <bskeggs@redhat.com>
Subject: Re: [Nouveau] [PATCH] drm/nouveau: Fix pre-nv50 pageflip events (v4)
Date: Tue, 15 Dec 2015 09:04:37 -0800	[thread overview]
Message-ID: <20151215170437.GE18302@kroah.com> (raw)
In-Reply-To: <CACvgo53PUcP43isv85p2DVO5YtgBajm7_n5Thsg1Y7zzf+zsMQ@mail.gmail.com>

On Tue, Dec 15, 2015 at 03:17:21PM +0000, Emil Velikov wrote:
> On 15 December 2015 at 15:01, poma <pomidorabelisima@gmail.com> wrote:
> > On 15.12.2015 12:21, Emil Velikov wrote:
> >> On 15 December 2015 at 11:11, poma <pomidorabelisima@gmail.com> wrote:
> >>
> >>>
> >>> Apparently not reached @stable (stable: 4.3.3 2015-12-15),
> >>> so here's one more time.
> >>>
> >> It has reached 4.4-rcX and will get picked by the stable maintainer
> >> (Greg?) in due time. Meanwhile you can ask your distro maintainers to
> >> apply it locally until we get an official release that includes it.
> >>
> >> -Emil
> >>
> >
> > It is all but unknown ;)
> > https://bugzilla.redhat.com/show_bug.cgi?id=1281368
> >
> > Emil, the point is - if it has -not- reached stable@vger.kernel.org, how can it be applied, in the first place.
> >
> The same way many others do ? I'd imagine there is a tool/script which
> parses through the development tree, which would explain why (many?)
> people explicitly suppress git from sending an email yet things still
> work. There is extra information in the documentation [1] if you're
> interested.

Yes, this is in the queue, along with 276 other patches that I need to
apply as well.  The backlog is large this time of year, sorry.

greg k-h
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: poma <pomidorabelisima@gmail.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	David Airlie <airlied@linux.ie>,
	"# 3.13+" <stable@vger.kernel.org>,
	Mario Kleiner <mario.kleiner.de@gmail.com>,
	ML dri-devel <dri-devel@lists.freedesktop.org>,
	Ikey Doherty <ikey@solus-project.com>,
	Ben Skeggs <bskeggs@redhat.com>,
	russianneuromancer@ya.ru,
	"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Thierry Reding <treding@nvidia.com>
Subject: Re: [Nouveau] [PATCH] drm/nouveau: Fix pre-nv50 pageflip events (v4)
Date: Tue, 15 Dec 2015 09:04:37 -0800	[thread overview]
Message-ID: <20151215170437.GE18302@kroah.com> (raw)
In-Reply-To: <CACvgo53PUcP43isv85p2DVO5YtgBajm7_n5Thsg1Y7zzf+zsMQ@mail.gmail.com>

On Tue, Dec 15, 2015 at 03:17:21PM +0000, Emil Velikov wrote:
> On 15 December 2015 at 15:01, poma <pomidorabelisima@gmail.com> wrote:
> > On 15.12.2015 12:21, Emil Velikov wrote:
> >> On 15 December 2015 at 11:11, poma <pomidorabelisima@gmail.com> wrote:
> >>
> >>>
> >>> Apparently not reached @stable (stable: 4.3.3 2015-12-15),
> >>> so here's one more time.
> >>>
> >> It has reached 4.4-rcX and will get picked by the stable maintainer
> >> (Greg?) in due time. Meanwhile you can ask your distro maintainers to
> >> apply it locally until we get an official release that includes it.
> >>
> >> -Emil
> >>
> >
> > It is all but unknown ;)
> > https://bugzilla.redhat.com/show_bug.cgi?id=1281368
> >
> > Emil, the point is - if it has -not- reached stable@vger.kernel.org, how can it be applied, in the first place.
> >
> The same way many others do ? I'd imagine there is a tool/script which
> parses through the development tree, which would explain why (many?)
> people explicitly suppress git from sending an email yet things still
> work. There is extra information in the documentation [1] if you're
> interested.

Yes, this is in the queue, along with 276 other patches that I need to
apply as well.  The backlog is large this time of year, sorry.

greg k-h

  reply	other threads:[~2015-12-15 17:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 16:37 [PATCH] drm/nouveau: Fix pre-nv50 pageflip events (v4) Thierry Reding
2015-11-10 16:41 ` Thierry Reding
2015-12-15 11:11   ` poma
     [not found]     ` <566FF56C.8000803-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-12-15 11:21       ` Emil Velikov
2015-12-15 11:21         ` [Nouveau] " Emil Velikov
2015-12-15 15:01         ` poma
2015-12-15 15:01           ` poma
2015-12-15 15:17           ` Emil Velikov
2015-12-15 17:04             ` Greg KH [this message]
2015-12-15 17:04               ` Greg KH

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=20151215170437.GE18302@kroah.com \
    --to=greg@kroah.com \
    --cc=bskeggs@redhat.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=ikey@solus-project.com \
    --cc=nouveau@lists.freedesktop.org \
    --cc=russianneuromancer@ya.ru \
    --cc=stable@vger.kernel.org \
    --cc=treding@nvidia.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.