public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Joe Thornber <thornber@redhat.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.3-mm1
Date: Thu, 19 Feb 2004 12:52:19 +0100	[thread overview]
Message-ID: <20040219125219.54978b4e.ak@suse.de> (raw)
In-Reply-To: <20040218134558.GN27549@reti>

On Wed, 18 Feb 2004 13:45:58 +0000
Joe Thornber <thornber@redhat.com> wrote:

> On Thu, Feb 19, 2004 at 07:37:34AM +0100, Andi Kleen wrote:
> > Supporting metadata can be quite simple - e.g. a standard header on the first blocks that
> > has a length and a number of records with unique IDs. And the kernel driver would need
> > to skip over these headers.
> 
> The target already takes an offset into the device, so you have what you want.

Ok fine. The only requirement would be compatible IVs then.

-Andi

  reply	other threads:[~2004-02-18 13:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040217232130.61667965.akpm@osdl.org.suse.lists.linux.kernel>
2004-02-18 10:43 ` 2.6.3-mm1 Andi Kleen
2004-02-18 10:55   ` 2.6.3-mm1 Andrew Morton
2004-02-19  6:37     ` 2.6.3-mm1 Andi Kleen
2004-02-18 13:45       ` 2.6.3-mm1 Joe Thornber
2004-02-19 11:52         ` Andi Kleen [this message]
2004-02-18 23:27           ` 2.6.3-mm1 Andrew Morton
2004-02-19 17:54             ` 2.6.3-mm1 Andi Kleen
     [not found] <1qujU-5xX-31@gated-at.bofh.it>
     [not found] ` <1qCUf-4vn-41@gated-at.bofh.it>
     [not found]   ` <1qGuR-bb-25@gated-at.bofh.it>
     [not found]     ` <1qGO2-uG-13@gated-at.bofh.it>
     [not found]       ` <1qGO5-uG-21@gated-at.bofh.it>
     [not found]         ` <1qGY1-RT-29@gated-at.bofh.it>
     [not found]           ` <1qGY1-RT-27@gated-at.bofh.it>
     [not found]             ` <1qIn3-5yq-23@gated-at.bofh.it>
2004-02-19 21:58               ` 2.6.3-mm1 Bill Davidsen
2004-02-19 22:01                 ` 2.6.3-mm1 Christophe Saout
2004-02-18  7:21 2.6.3-mm1 Andrew Morton
2004-02-18  7:43 ` 2.6.3-mm1 Andrew Morton
2004-02-18  9:25   ` 2.6.3-mm1 Andrew Morton
2004-02-18 13:42     ` 2.6.3-mm1 Rusty Russell
2004-02-18 18:50       ` 2.6.3-mm1 Andrew Morton
2004-02-18 11:13 ` 2.6.3-mm1 Sean Neakums
2004-02-18 11:14 ` 2.6.3-mm1 Jonathan Brown
2004-02-18 12:37   ` 2.6.3-mm1 Sean Neakums
2004-02-18 14:26 ` 2.6.3-mm1 Ramon Rey Vicente
2004-02-18 18:55   ` 2.6.3-mm1 Andrew Morton
2004-02-18 19:06     ` 2.6.3-mm1 Matthew Wilcox
2004-02-18 16:16 ` 2.6.3-mm1 Bill Davidsen
2004-02-18 20:04   ` 2.6.3-mm1 Brandon Low
2004-02-18 20:22     ` 2.6.3-mm1 Andrew Morton
2004-02-18 20:33       ` 2.6.3-mm1 Brandon Low
2004-02-18 20:52         ` 2.6.3-mm1 Andrew Morton
2004-02-18 20:52           ` 2.6.3-mm1 Brandon Low
2004-02-18 21:00             ` 2.6.3-mm1 Andrew Morton
2004-02-18 22:15             ` 2.6.3-mm1 Christophe Saout
2004-02-19  0:33               ` 2.6.3-mm1 Brandon Low
2004-02-19 12:39                 ` 2.6.3-mm1 Christophe Saout
2004-02-18 17:50 ` 2.6.3-mm1 James Simmons
2004-02-22  2:46 ` 2.6.3-mm1 William Lee Irwin III

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=20040219125219.54978b4e.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thornber@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox