From: Andrew Morton <akpm@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Howells <dhowells@redhat.com>,
jirislaby@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix a const assignment in moxa_load_fw()
Date: Fri, 11 Jul 2008 12:20:56 -0700 [thread overview]
Message-ID: <20080711122056.8b36c084.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080708171029.08db0f4d@the-village.bc.nu>
On Tue, 8 Jul 2008 17:10:29 +0100 Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Tue, 08 Jul 2008 16:44:16 +0100
> David Howells <dhowells@redhat.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@redhat.com>
>
> Acked-by: Alan Cox <alan@redhat.com>
Appears to already be fixed in linux-next, perhaps by this:
commit b30a6a47716ba1a5112b44f0a3962daff961935e
Author: Alan Cox <alan@redhat.com>
Date: Fri Jul 4 19:18:14 2008 +1000
83-tty-moxa-warning
Signed-off-by: Alan Cox <alan@redhat.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.
next prev parent reply other threads:[~2008-07-11 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 15:44 David Howells
2008-07-08 16:10 ` Alan Cox
2008-07-11 19:20 ` Andrew Morton [this message]
2008-07-11 23:26 ` Stephen Rothwell
2008-07-11 22:48 ` David Howells
2008-07-11 22:58 ` Andrew Morton
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=20080711122056.8b36c084.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dhowells@redhat.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome