From: akpm@linux-foundation.org
To: vlada.peric@gmail.com, dilinger@debian.org, mm-commits@vger.kernel.org
Subject: [merged] asiliantfb-add-missing-return-statement.patch removed from -mm tree
Date: Wed, 22 Apr 2009 11:29:21 -0700 [thread overview]
Message-ID: <200904221829.n3MITL30005514@imap1.linux-foundation.org> (raw)
The patch titled
asiliantfb: add missing return statement
has been removed from the -mm tree. Its filename was
asiliantfb-add-missing-return-statement.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: asiliantfb: add missing return statement
From: Vlada Peric <vlada.peric@gmail.com>
Commit 032220ba (asiliantfb: fix cmap memory leaks) changed the function
init_asiliant from void to int, resulting in the following compile warning:
drivers/video/asiliantfb.c: In function `init_asiliant':
drivers/video/asiliantfb.c:536: warning: control reaches end of
non-void function
Fix the warning by returning 0.
Signed-off-by: Vlada Peric <vlada.peric@gmail.com>
Cc: Andres Salomon <dilinger@debian.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/video/asiliantfb.c | 1 +
1 file changed, 1 insertion(+)
diff -puN drivers/video/asiliantfb.c~asiliantfb-add-missing-return-statement drivers/video/asiliantfb.c
--- a/drivers/video/asiliantfb.c~asiliantfb-add-missing-return-statement
+++ a/drivers/video/asiliantfb.c
@@ -533,6 +533,7 @@ static int __devinit init_asiliant(struc
writeb(0xff, mmio_base + 0x78c);
chips_hw_init(p);
+ return 0;
}
static int __devinit
_
Patches currently in -mm which might be from vlada.peric@gmail.com are
reply other threads:[~2009-04-22 18:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200904221829.n3MITL30005514@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dilinger@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=vlada.peric@gmail.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.