From: Adrian Bunk <bunk@stusta.de>
To: dm-devel@redhat.com, Jeff Mahoney <jeffm@suse.com>,
Alasdair G Kergon <agk@redhat.com>,
Michal Miroslaw <mirq-linux@rere.qmqm.pl>,
Daniel Kobras <kobras@linux.de>, Neil Brown <neilb@suse.de>,
Mark McLoughlin <markmc@redhat.com>
Subject: Re: RFC: dm patches for 2.6.16
Date: Thu, 14 Dec 2006 23:13:27 +0100 [thread overview]
Message-ID: <20061214221327.GP3388@stusta.de> (raw)
In-Reply-To: <20061205202559.GY4409@agk.surrey.redhat.com>
On Tue, Dec 05, 2006 at 08:25:59PM +0000, Alasdair G Kergon wrote:
> On Fri, Nov 24, 2006 at 04:24:44AM +0100, Adrian Bunk wrote:
> > The following attached patches seem to make sense for 2.6.16:
> >
> > Added in 2.6.17.11 and 2.6.18:
> > dm: BUG/OOPS fix
> >
> > Added in 2.6.17.12 and 2.6.18:
> > dm snapshot: unify chunk_size
> > dm: add module ref counting
> > dm: mirror sector offset fix
> > dm: Fix deadlock under high i/o load in raid1 setup.
> >
> > Added in 2.6.19:
> > dm snapshot: fix metadata writing when suspending
> >
> > Do these patches look OK for 2.6.16,
>
> Yes.
Thanks, I've applied them.
> > Are there any critical patches I missed?
>
> The general rule for patches I send to linux-kernel is that any patch with
> 'fix' in the title is a candidate for stable trees (together with any
> earlier patches they depend upon).
I do _sometimes_ find patches for 2.6.16 on linux-kernel.
I'm regularly going through the patches that have been applied to
-stable.
AFAIK Greg and Chris only apply patches to -stable that were explicitely
sent to stable@kernel.org.
It would therefore be good, if you could send such patches explicitely
to stable@kernel.org.
> Alasdair
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2006-12-14 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 3:24 RFC: dm patches for 2.6.16 Adrian Bunk
2006-12-05 20:25 ` Alasdair G Kergon
2006-12-14 22:13 ` Adrian Bunk [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=20061214221327.GP3388@stusta.de \
--to=bunk@stusta.de \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jeffm@suse.com \
--cc=kobras@linux.de \
--cc=markmc@redhat.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=neilb@suse.de \
/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.