From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Rickard Strandqvist <rickard_strandqvist@spectrumdigital.se>
Cc: Karsten Keil <isdn@linux-pingi.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] isdn: hisax: l3dss1.c: Fix for possible null pointer dereference
Date: Tue, 20 May 2014 16:23:23 +0400 [thread overview]
Message-ID: <537B493B.8020008@cogentembedded.com> (raw)
In-Reply-To: <CAFo99gb3fOq=kXwiG=LsvRXHdgazQWv3t6XZqDOtRHc+FLxCbw@mail.gmail.com>
Hello.
On 20-05-2014 1:56, Rickard Strandqvist wrote:
> Hi Sergei
> I did not put the assignment in the if statement.
You didn't but you changed the line it's on (which wasn't required BTW).
> Is it meant for me
> to change all the code around the parts I fix?
No, the patch just needs to be checkpatch.pl-clean.
> There are many assignments in if in the l3dss1_cmd_global() funktion.
You can leave them alone for now. You can also leave alone the line I was
referring to.
> It's late and I'm tired, but I still can not see which of these pairs
> of features that I can remove ...?
> if (ic->parm.dss1_io.timeout > 0) {
> if (!(pc = dss1_new_l3_process(st, -1))) {
> free_invoke_id(st, id);
> return (-2);
> }
> pc->prot.dss1.ll_id = ic->parm.dss1_io.ll_id; /* remember id */
> pc->prot.dss1.proc = ic->parm.dss1_io.proc; /* and procedure */
> }
I didn't quite get the question, if you were asking me.
> Best regards
> Rickard Strandqvist
WBR, Sergei
next prev parent reply other threads:[~2014-05-20 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 21:24 [PATCH] isdn: hisax: l3dss1.c: Fix for possible null pointer dereference Rickard Strandqvist
2014-05-19 21:26 ` Sergei Shtylyov
2014-05-19 21:56 ` Rickard Strandqvist
2014-05-20 12:23 ` Sergei Shtylyov [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-17 17:18 Rickard Strandqvist
2014-05-19 1:12 ` David Miller
2014-05-19 21:18 ` Rickard Strandqvist
2014-05-19 21:24 ` Sergei Shtylyov
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=537B493B.8020008@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rickard_strandqvist@spectrumdigital.se \
/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.