From: Valdis.Kletnieks@vt.edu
To: Mike Anderson <andmike@us.ibm.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Matt Mackall <mpm@selenic.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Alasdair G Kergon <agk@redhat.com>
Subject: Re: [dm-devel] Re: [2.6.23 PATCH 13/18] dm: netlink
Date: Fri, 13 Jul 2007 16:12:58 -0400 [thread overview]
Message-ID: <6408.1184357578@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 12 Jul 2007 19:00:59 PDT." <20070713020059.GA5402@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
On Thu, 12 Jul 2007 19:00:59 PDT, Mike Anderson said:
> No, all admin tools and interfaces function as they do today. The
> dm-netlink patch series only contains 9 deletions (actual just one true
> deletion of existing kernel code the others are due to break up of the
> patch into compilable chunks). The intent was not to break users or force
> migration.
OK, I'll bite - if the admin tools function as before, who is *using* the
code? Or do the admin tools have a preferred netlink component and a fallback
set of code if that fails?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-07-13 20:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 21:01 Alasdair G Kergon
2007-07-11 21:27 ` Andrew Morton
2007-07-11 23:37 ` Mike Anderson
2007-07-12 8:10 ` Evgeniy Polyakov
2007-07-12 10:27 ` David Miller
2007-07-12 13:42 ` Mike Anderson
2007-07-12 23:19 ` Matt Mackall
2007-07-12 23:31 ` Andrew Morton
2007-07-13 2:00 ` [dm-devel] " Mike Anderson
2007-07-13 20:12 ` Valdis.Kletnieks [this message]
2007-07-13 7:03 ` Evgeniy Polyakov
2007-07-13 7:16 ` Kay Sievers
2007-07-12 23:45 ` Mike Anderson
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=6408.1184357578@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=agk@redhat.com \
--cc=andmike@us.ibm.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@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
all inboxes | Powered by JetHome®