linux-kernel - Re: [PATCH] Staging: tidspbridge: fixed several coding style issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <AANLkTi=a+nkQ16ngpkztKdGwriGdMFA=jFVQGQH0Niok@mail.gmail.com>
Date:	Thu, 17 Feb 2011 15:21:05 -0600
From:	"Ramirez Luna, Omar" <omar.ramirez@...com>
To:	Dan Carpenter <error27@...il.com>,
	Klaas Neirinck <klaas.neirinck@...il.com>, gregkh@...e.de,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Staging: tidspbridge: fixed several coding style issues

Hi,

On Fri, Feb 11, 2011 at 2:01 AM, Dan Carpenter <error27@...il.com> wrote:
> On Fri, Feb 11, 2011 at 01:02:46AM +0100, Klaas Neirinck wrote:
>> Fixed several coding style issues.
>>
>> Signed-off-by: Klaas Neirinck <klaas.neirinck@...il.com>
> ---                             dest = ibuf.bufr;
>>  #ifdef OPT_ZERO_COPY_LOADER
>>                               zero_copy = false;
>> -                             if (!dload_check_type(sptr, DLOAD_CINIT) {
>> +                             if (!dload_check_type(sptr, DLOAD_CINIT)) {
>>                                       dlthis->myio->writemem(dlthis->myio,
>>                                                              &dest,
>
> Also it apparently fixes a compile problem?  Why not say that in the
> change log...  :/

I don't think this is present in staging-next anymore.

OPT_ZERO_COPY_LOADER was removed as it was dead code.

Regards,

Omar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/