Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: David Butterfield <dab21774@gmail.com>
To: drbd-dev@lists.linbit.com, Lars Ellenberg <lars.ellenberg@linbit.com>
Subject: Re: [Drbd-dev] main.c comments
Date: Tue, 18 Jun 2019 11:58:54 -0600	[thread overview]
Message-ID: <c60379e8-7117-0c80-3371-2a6f0e93fd41@gmail.com> (raw)
In-Reply-To: <20190612142612.GB5803@soda.linbit>

>> (1) Isn't the third argument to module_param_named() supposed to be the type of
>>     the second argument?  (But seems to require it as a single token??)
> 
> Yes and no ;-)
> the type of the second argument in this case is a drbd_protocol_version,
> so by naming that as third argument, we point to the "conversion and
> validation functions" for that type.

Aha!  Thanks.  All I was doing was comparing the types at compile-time
and not finding a match.

> again, "details depend on the kernel version"...

Yeah, I'm pretending to be 2.6.32, the minimum supported by DRBD's kernel
compatibility, to minimize the amount of kernel function I have to emulate.

>> (2) The cast avoids a compiler warning about signed/unsigned comparison.
> 
> As long as our kernel compiles complete without warnings, "boring".

OK, I'll set my own warnings back down to the same ones the kernel enables.

For warnings that happen a lot I already disabled them, but there were
three warnings that each was reported only once in 51,444 lines of DRBD
code -- I had figured those conditions were being maintained and not
supposed to be there, so those are the ones I mentioned.

David Butterfield

  reply	other threads:[~2019-06-18 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 16:15 [Drbd-dev] main.c comments David Butterfield
2019-06-12 14:26 ` Lars Ellenberg
2019-06-18 17:58   ` David Butterfield [this message]
2019-06-18 19:45   ` [Drbd-dev] q->queue_lock initialization David Butterfield

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=c60379e8-7117-0c80-3371-2a6f0e93fd41@gmail.com \
    --to=dab21774@gmail.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=lars.ellenberg@linbit.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