From: Lou Langholtz <ldl@aros.net>
To: shrybman@sympatico.ca
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>,
Paul Clements <Paul.Clements@SteelEye.com>
Subject: [PATCH] nbd.c compile warning
Date: Sat, 12 Jul 2003 11:04:45 -0600 [thread overview]
Message-ID: <3F103FAD.4050506@aros.net> (raw)
Do you have large block device support turned on or off in your kernel
build options? I believe this compile warning came as a result of
compiling without CONFIG_LBD - I hadn't tried building that way and
would then have missed this problem. Just typecasting the result as your
patch does should work correctly either way though. I'll make sure to
pull it into my NBD sources but you will need to get Andrew Morton or
Paul Clements to pick up the patch for it to move into the kernel distro
stream. I've CC'd them on this message to help expedite this. Thanks!
next reply other threads:[~2003-07-12 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 17:04 Lou Langholtz [this message]
2003-07-12 18:35 ` [PATCH] nbd.c compile warning Shane Shrybman
-- strict thread matches above, loose matches on Subject: below --
2003-07-12 14:50 Shane Shrybman
2003-07-13 17:16 ` Paul Clements
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=3F103FAD.4050506@aros.net \
--to=ldl@aros.net \
--cc=Paul.Clements@SteelEye.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shrybman@sympatico.ca \
/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.