From: Andrew Morton <akpm@osdl.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: aia21@cam.ac.uk, torvalds@osdl.org, linux-kernel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net
Subject: Re: [2.6-BK-URL] NTFS 2.1.22 - Bug and race fixes and improved error handling.
Date: Tue, 16 Nov 2004 19:20:49 -0800 [thread overview]
Message-ID: <20041116192049.0ca4efa3.akpm@osdl.org> (raw)
In-Reply-To: <1100644656.17573.0.camel@krustophenia.net>
Lee Revell <rlrevell@joe-job.com> wrote:
>
> On Wed, 2004-11-10 at 13:42 +0000, Anton Altaparmakov wrote:
> > Hi Linus, Hi Andrew, please do a
> >
> > bk pull bk://linux-ntfs.bkbits.net/ntfs-2.6
> >
>
> New warning with 2.6.10-rc2-mm1:
>
> CC [M] fs/ntfs/super.o
> fs/ntfs/super.c: In function `__get_nr_free_mft_records':
> fs/ntfs/super.c:2105: warning: initialization from incompatible pointer type
That's my whacky hack to detect kunmap_atomic() bugs. I'll fix things up,
thanks.
prev parent reply other threads:[~2004-11-17 3:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 13:42 [2.6-BK-URL] NTFS 2.1.22 - Bug and race fixes and improved error handling Anton Altaparmakov
2004-11-16 22:37 ` Lee Revell
2004-11-17 3:20 ` Andrew Morton [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=20041116192049.0ca4efa3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=rlrevell@joe-job.com \
--cc=torvalds@osdl.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