linux-kernel - Re: [PATCH] Fix a const assignment in moxa_load

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080711122056.8b36c084.akpm@linux-foundation.org>
Date:	Fri, 11 Jul 2008 12:20:56 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	David Howells <dhowells@...hat.com>, jirislaby@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix a const assignment in moxa_load_fw()

On Tue, 8 Jul 2008 17:10:29 +0100 Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

> On Tue, 08 Jul 2008 16:44:16 +0100
> David Howells <dhowells@...hat.com> wrote:
> 
> > Fix an assignment of a const pointer to a non-const pointer in moxa_load_fw().
> > 
> > This was introduced by patch 037182346f0991683cc7320a257c3f6089432cee.
> > 
> > Signed-off-by: David Howells <dhowells@...hat.com>
> 
> Acked-by: Alan Cox <alan@...hat.com>

Appears to already be fixed in linux-next, perhaps by this:

commit b30a6a47716ba1a5112b44f0a3962daff961935e
Author: Alan Cox <alan@...hat.com>
Date:   Fri Jul 4 19:18:14 2008 +1000

    83-tty-moxa-warning
    
    Signed-off-by: Alan Cox <alan@...hat.com>

which, err, isn't in today's linux-next because the whole tty tree got
accidentally dropped.  Not that this was a tty patch.

Hopefully the patches in this tree will get title and changelog repairs
before they go much further.  I suspect a lot of this damage was due to
incompatibility between Alan's patch-file format and the expectations of
Stephen's scripts.
--
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/