From: "Paul B. Henson" <henson@acm.org>
To: 'Mike Snitzer' <snitzer@redhat.com>
Cc: 'device-mapper development' <dm-devel@redhat.com>
Subject: Re: dm-cache questions
Date: Wed, 11 Dec 2013 18:14:29 -0800 [thread overview]
Message-ID: <0c4901cef6df$e557cec0$b0076c40$@acm.org> (raw)
In-Reply-To: <20131211150644.GA28188@redhat.com>
> From: Mike Snitzer [mailto:snitzer@redhat.com]
> Sent: Wednesday, December 11, 2013 7:07 AM
>
> 3.10 is actively maintained by gregkh as a "longterm" stable kernel so
> all relevant upstream commits should make their way into that tree:
Right, but as dm-cache changes over time, with new features or other major
changes being made relative to the version shipped in 3.10, presumably some
bug fixes that might get committed to mainline would not apply cleanly to
3.10 without some potentially non-negligible backporting effort? I don't
think gregkh does that himself? So if there was a major bug fix that ideally
would go back to LTS but couldn't be simply cherry picked, one of the
dm-cache devs would need to submit a separate commit for 3.10? Or perhaps I
misunderstand the process.
next prev parent reply other threads:[~2013-12-12 2:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 1:56 dm-cache questions Paul B. Henson
2013-12-10 9:50 ` Joe Thornber
2013-12-10 21:04 ` Paul B. Henson
2013-12-11 1:03 ` Alasdair G Kergon
2013-12-11 2:08 ` Paul B. Henson
2013-12-11 15:06 ` Mike Snitzer
2013-12-12 2:14 ` Paul B. Henson [this message]
2013-12-13 14:20 ` Mike Snitzer
2013-12-13 19:44 ` Paul B. Henson
2013-12-13 21:21 ` Mike Snitzer
2013-12-14 0:59 ` Paul B. Henson
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='0c4901cef6df$e557cec0$b0076c40$@acm.org' \
--to=henson@acm.org \
--cc=dm-devel@redhat.com \
--cc=snitzer@redhat.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.