From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Benjamin Romer <benjamin.romer@unisys.com>,
David Kershner <david.kershner@unisys.com>,
sparmaintainer@unisys.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: unisys: remove comparison
Date: Thu, 12 Mar 2015 15:22:22 +0100 [thread overview]
Message-ID: <20150312142222.GA19785@kroah.com> (raw)
In-Reply-To: <1426169661-15142-2-git-send-email-sudipm.mukherjee@gmail.com>
On Thu, Mar 12, 2015 at 07:44:21PM +0530, Sudip Mukherjee wrote:
> the macro comparison is always true as MAJOR is defined as
> unsiged int.
>
> Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> ---
> drivers/staging/unisys/visorchipset/file.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/unisys/visorchipset/file.c b/drivers/staging/unisys/visorchipset/file.c
> index 9ca7f1e..a1e8e79 100644
> --- a/drivers/staging/unisys/visorchipset/file.c
> +++ b/drivers/staging/unisys/visorchipset/file.c
> @@ -82,10 +82,8 @@ visorchipset_file_cleanup(void)
> cdev_del(&file_cdev);
> file_cdev.ops = NULL;
> if (registered) {
> - if (MAJOR(majordev) >= 0) {
> - unregister_chrdev_region(majordev, 1);
> - majordev = MKDEV(0, 0);
> - }
> + unregister_chrdev_region(majordev, 1);
> + majordev = MKDEV(0, 0);
If this is really true, then why is someone trying to assign -1 to
majordev at the top of the file? :)
I suggest you fix this up properly, not by papering over the bug.
thanks,
greg k-h
next prev parent reply other threads:[~2015-03-12 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 14:14 [PATCH 1/2] staging: unisys: remove unused variables Sudip Mukherjee
2015-03-12 14:14 ` [PATCH 2/2] staging: unisys: remove comparison Sudip Mukherjee
2015-03-12 14:22 ` Greg Kroah-Hartman [this message]
2015-03-16 15:34 ` [PATCH 1/2] staging: unisys: remove unused variables Greg Kroah-Hartman
2015-03-17 14:06 ` 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=20150312142222.GA19785@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benjamin.romer@unisys.com \
--cc=david.kershner@unisys.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparmaintainer@unisys.com \
--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