All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: stable@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [PATCH 3.10,3.14] dm snapshot: allocate a per-target structure for snapshot-origin target
Date: Mon, 29 Jun 2015 17:22:44 -0700	[thread overview]
Message-ID: <20150630002244.GD6430@kroah.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1506031056520.14129@file01.intranet.prod.int.rdu2.redhat.com>

On Wed, Jun 03, 2015 at 11:00:16AM -0400, Mikulas Patocka wrote:
> This is backport of 599cdf3bfbe21fe94f4416c9e54363b285c9532a for 3.10 and 
> 3.14 kernels. The patch doesn't fix any bug but it is needed for other 
> backported patches.

You sent 5 patches, with no hint as to the order to apply them in :(

Also, these are really big for such old kernels, are they really all
needed?  Why can't people just use 4.0 and newer kernels if they have
these issues?

thanks,

greg k-h

      reply	other threads:[~2015-06-30  0:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 15:00 [PATCH 3.10,3.14] dm snapshot: allocate a per-target structure for snapshot-origin target Mikulas Patocka
2015-06-30  0:22 ` Greg KH [this message]

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=20150630002244.GD6430@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@redhat.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 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.