From: Oscar Carter <oscar.carter@gmx.com>
To: "Lev R. Oshvang ." <levonshe@gmail.com>
Cc: alsa-devel@alsa-project.org,
linux1394-devel@lists.sourceforge.net,
Oscar Carter <oscar.carter@gmx.com>,
Kees Cook <keescook@chromium.org>,
kernel-hardening@lists.openwall.com,
linux-kernel@vger.kernel.org,
Clemens Ladisch <clemens@ladisch.de>,
Takashi Iwai <tiwai@suse.com>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] firewire: Remove function callback casts
Date: Tue, 19 May 2020 18:59:11 +0200 [thread overview]
Message-ID: <20200519165910.GA3187@ubuntu> (raw)
In-Reply-To: <CAP22eLF2Q3O+=tnHRKE5q=jn9gw2G1rjAKiewM4qGsf4WYvP0Q@mail.gmail.com>
On Sun, May 17, 2020 at 07:43:21PM +0300, Lev R. Oshvang . wrote:
>
> Hi Oscar,
> I would recommend to explicitly set NULL to _cb and use if elif to
> exclude the case where botm _cb paraneters are passed as NULLs :
> > +
> ctx->callback.mc =NULL:
> ctx->callback.sc = NULL;
> > + if (cb_sc)
> > + ctx->callback.sc = cb_sc;
>
> > + elif (cb_ms)
> > + ctx->callback.mc = cb_mc;
> > + else
> return -EINVAL;
Ok, I will do the changes you suggested and I will resend a new version.
> Hope you get the point.
> Lev
Thanks,
Oscar Carter
WARNING: multiple messages have this Message-ID (diff)
From: Oscar Carter <oscar.carter@gmx.com>
To: "Lev R. Oshvang ." <levonshe@gmail.com>
Cc: Oscar Carter <oscar.carter@gmx.com>,
Kees Cook <keescook@chromium.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Clemens Ladisch <clemens@ladisch.de>,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
kernel-hardening@lists.openwall.com,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] firewire: Remove function callback casts
Date: Tue, 19 May 2020 18:59:11 +0200 [thread overview]
Message-ID: <20200519165910.GA3187@ubuntu> (raw)
In-Reply-To: <CAP22eLF2Q3O+=tnHRKE5q=jn9gw2G1rjAKiewM4qGsf4WYvP0Q@mail.gmail.com>
On Sun, May 17, 2020 at 07:43:21PM +0300, Lev R. Oshvang . wrote:
>
> Hi Oscar,
> I would recommend to explicitly set NULL to _cb and use if elif to
> exclude the case where botm _cb paraneters are passed as NULLs :
> > +
> ctx->callback.mc =NULL:
> ctx->callback.sc = NULL;
> > + if (cb_sc)
> > + ctx->callback.sc = cb_sc;
>
> > + elif (cb_ms)
> > + ctx->callback.mc = cb_mc;
> > + else
> return -EINVAL;
Ok, I will do the changes you suggested and I will resend a new version.
> Hope you get the point.
> Lev
Thanks,
Oscar Carter
next prev parent reply other threads:[~2020-05-19 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 17:39 [PATCH] firewire: Remove function callback casts Oscar Carter
2020-05-16 17:39 ` Oscar Carter
2020-05-17 16:43 ` Lev R. Oshvang .
2020-05-17 16:43 ` Lev R. Oshvang .
2020-05-19 16:59 ` Oscar Carter [this message]
2020-05-19 16:59 ` Oscar Carter
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=20200519165910.GA3187@ubuntu \
--to=oscar.carter@gmx.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=levonshe@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=mchehab@kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=tiwai@suse.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 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.