linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Dave Stevenson <dave.stevenson@raspberrypi.org>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	mchehab@kernel.org, linux-media@vger.kernel.org,
	Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v2 for v4.4 1/1] v4l: event: Add subscription to list before calling "add" operation
Date: Mon, 19 Nov 2018 18:46:21 +0100	[thread overview]
Message-ID: <20181119174621.GA13098@kroah.com> (raw)
In-Reply-To: <20181119170354.kjgob6m2lsbqae2m@kekkonen.localdomain>

On Mon, Nov 19, 2018 at 07:03:54PM +0200, Sakari Ailus wrote:
> Hi Greg,
> 
> On Mon, Nov 19, 2018 at 04:14:00PM +0100, Greg Kroah-Hartman wrote:
> > On Wed, Nov 14, 2018 at 11:37:46AM +0200, Sakari Ailus wrote:
> > > [ upstream commit 92539d3eda2c090b382699bbb896d4b54e9bdece ]
> > 
> > There is no such git commit id in Linus's tree :(
> 
> Right. At the moment it's in the media tree only. I expect it'll end up to
> Linus's tree once Mauro will send the next pull request from the media tree
> to Linus.

Ok, please do not send requests for stable tree inclusion until _AFTER_
the patch is in Linus's tree, otherwise it just wastes the stable tree
maintainer's time :(

greg k-h

  reply	other threads:[~2018-11-20  4:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14  9:37 [PATCH v2 for v4.4 1/1] v4l: event: Add subscription to list before calling "add" operation Sakari Ailus
2018-11-19 15:14 ` Greg Kroah-Hartman
2018-11-19 17:03   ` Sakari Ailus
2018-11-19 17:46     ` Greg Kroah-Hartman [this message]
2018-11-20 10:49       ` Sakari Ailus
2018-11-20 11:21         ` Mauro Carvalho Chehab
2018-11-22 11:33           ` Sakari Ailus
2018-11-26  7:27             ` Greg Kroah-Hartman
2018-11-26  7:30               ` Greg Kroah-Hartman

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=20181119174621.GA13098@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dave.stevenson@raspberrypi.org \
    --cc=hans.verkuil@cisco.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sashal@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).