public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lubomir Rintel <lkundrak@v3.sk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] V7: Add support for non-PDP11 v7 filesystems
Date: Tue, 27 Jul 2010 02:19:15 +0200	[thread overview]
Message-ID: <1280189955.26200.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20100726165231.ea38062e.akpm@linux-foundation.org>

On Mon, 2010-07-26 at 16:52 -0700, Andrew Morton wrote:
> On Mon, 26 Jul 2010 00:59:16 +0200
> Lubomir Rintel <lkundrak@v3.sk> wrote:
> 
> > This adds byte order autodetection (of PDP-11 and LE filesystems).
> > No attempt is made to detect big-endian filesystems -- were there any?
> > Tested with PDP-11 v7 filesystems and PC-IX maintenance floppy.
> 
> Which kernel is this against?  My v7_fill_super() is significantly
> different from yours.

This depends on [PATCH] V7: Adjust sanity checks for some volumes
<1279761108-302-1-git-send-email-lkundrak@v3.sk>.

It might be that I've messed up something in the communication so that
the dependency was not immediately clear. To be honest, I'm not very
familiar with the way reviews and adjustements to patches are tracked.
What have I done wrong, here? How am I supposed to follow up with a
change to a single patch of a multi-patch (be it just two in this case)
set?

-- 
Flash is the Web2.0 version of blink and animated gifs.
                                     -- Stephen Smoogen


  reply	other threads:[~2010-07-27  0:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 17:16 A few V7 fs improvements Lubomir Rintel
2010-07-19 14:53 ` Christoph Hellwig
2010-07-19 16:10 ` Bill Davidsen
2010-07-19 17:16 ` [PATCH 1/3] [fs/sysv] Add v7 alias Lubomir Rintel
2010-07-19 14:53   ` Christoph Hellwig
2010-07-19 17:16   ` [PATCH 2/3] [fs/sysv] V7: Adjust sanity checks for some volumes Lubomir Rintel
2010-07-19 14:54     ` Christoph Hellwig
2010-07-20 10:31       ` Lubomir Rintel
2010-07-22  1:11         ` [PATCH] " Lubomir Rintel
2010-07-19 17:16     ` [PATCH 3/3] [fs/sysv] V7: Add support for non-PDP11 v7 filesystems Lubomir Rintel
2010-07-19 14:58       ` Christoph Hellwig
2010-07-20 10:41         ` Lubomir Rintel
2010-07-22  1:17           ` Lubomir Rintel
2010-07-22  1:18             ` [PATCH] " Lubomir Rintel
2010-07-24 13:51         ` [PATCH 3/3] [fs/sysv] " Al Viro
2010-07-25 22:59           ` [PATCH] " Lubomir Rintel
2010-07-26  0:26             ` Randy Dunlap
2010-07-26 23:52             ` Andrew Morton
2010-07-27  0:19               ` Lubomir Rintel [this message]
2010-07-27  0:29                 ` Andrew Morton
2010-07-25  5:23 ` A few V7 fs improvements Artem Bityutskiy
  -- strict thread matches above, loose matches on Subject: below --
2010-07-25 22:50 [PATCH] V7: Add support for non-PDP11 v7 filesystems Lubomir Rintel
2010-07-25 22:54 ` Lubomir Rintel

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=1280189955.26200.5.camel@localhost.localdomain \
    --to=lkundrak@v3.sk \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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