From: "Giedrius Statkevičius" <giedrius.statkevicius@gmail.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] staging: sm750fb: fix undeclared function
Date: Sun, 08 Mar 2015 13:02:45 +0000 [thread overview]
Message-ID: <54FC4875.1050800@gmail.com> (raw)
In-Reply-To: <1425817886-14387-4-git-send-email-sudipm.mukherjee@gmail.com>
On 2015.03.08 14:31, Sudip Mukherjee wrote:
> kbuild test robot reported that for microblaze-allyesconfig
> chan_to_field() and lynxfb_ops_set_par() were not defined. These two
> functions were defined under CONFIG_PM, so for any archtecture if
> CONFIG_PM is not defined we will have this error.
> while moving the lynxfb_suspend() function some very obvious
> checkpatch errors were taken care of.
Such as? If you do you could also fix up the poor things with that
function too such as the comment style here (no space between ; and the
comment):
> + if (info)
> + fb_set_suspend(info, 1);/* 1 means do suspend*/
> +
or here (extra unneeded spaces):
> +
> + /* set chip to sleep mode */
> + if (share->suspend)
> + (*share->suspend)(share);
--
Thanks,
Giedrius
next prev parent reply other threads:[~2015-03-08 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 12:43 [PATCH 1/4] staging: sm750fb: wrong type for print Sudip Mukherjee
2015-03-08 12:40 ` Giedrius Statkevičius
2015-03-08 12:59 ` Sudip Mukherjee
2015-03-08 12:43 ` [PATCH 2/4] staging: sm750fb: remove pragma optimize Sudip Mukherjee
2015-03-08 12:43 ` [PATCH 3/4] staging: sm750fb: correctly define SM750LE_REVISION_ID Sudip Mukherjee
2015-03-08 12:59 ` Giedrius Statkevičius
2015-03-08 17:43 ` Sudip Mukherjee
2015-03-08 12:43 ` [PATCH 4/4] staging: sm750fb: fix undeclared function Sudip Mukherjee
2015-03-08 13:02 ` Giedrius Statkevičius [this message]
2015-03-09 9:22 ` [PATCH 1/4] staging: sm750fb: wrong type for print Dan Carpenter
2015-03-09 9:47 ` Sudip Mukherjee
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=54FC4875.1050800@gmail.com \
--to=giedrius.statkevicius@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).