linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maciej Matraszek <m.matraszek@samsung.com>
To: Greg KH <greg@kroah.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mauro Carvalho Chehab <m.chehab@samsung.com>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	stable@vger.kernel.org,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: [PATCH v2] [media] v4l2-common: fix overflow in v4l_bound_align_image()
Date: Fri, 12 Sep 2014 18:11:49 +0200	[thread overview]
Message-ID: <1410538309.8852.30.camel@AMDC723> (raw)
In-Reply-To: <20140910171013.GA14048@kroah.com>

On Wed, 2014-09-10 at 10:10 -0700, Greg KH wrote:
> > Fixes: b0d3159be9a3 ("V4L/DVB (11901): v4l2: Create helper function for bounding and aligning images")
> > Signed-off-by: Maciej Matraszek <m.matraszek@samsung.com>
> > Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > 
> > ---
> 
> <formletter>
> 
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
> for how to do this properly.
> 
> </formletter>

Hi Greg,

I'm really sorry for this mistake.
Do I understand correctly that it is just a missing
'Cc: <stable@vger.kernel.org>' line?
Are there any other issues?

Thanks for your patience,
Maciej Matraszek



  reply	other threads:[~2014-09-12 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 16:51 [PATCH v2] [media] v4l2-common: fix overflow in v4l_bound_align_image() Maciej Matraszek
2014-09-10 17:10 ` Greg KH
2014-09-12 16:11   ` Maciej Matraszek [this message]
2014-09-12 16:29     ` 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=1410538309.8852.30.camel@AMDC723 \
    --to=m.matraszek@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=greg@kroah.com \
    --cc=hans.verkuil@cisco.com \
    --cc=k.kozlowski@samsung.com \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=s.nawrocki@samsung.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=stable@vger.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).