From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Maninder Singh <maninder1.s@samsung.com>
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, pankaj.m@samsung.com
Subject: Re: [PATCH 1/1] staging/comedi: remove unnecessary check around pci_dev_put
Date: Thu, 25 Jun 2015 16:40:48 +0530 [thread overview]
Message-ID: <20150625111048.GA13366@sudip-PC> (raw)
In-Reply-To: <1435229426-39366-1-git-send-email-maninder1.s@samsung.com>
On Thu, Jun 25, 2015 at 04:20:26PM +0530, Maninder Singh wrote:
> pci_dev_put cehcks for NULL pointer itself,
did you mean checks?
regards
sudip
next prev parent reply other threads:[~2015-06-25 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 10:50 [PATCH 1/1] staging/comedi: remove unnecessary check around pci_dev_put Maninder Singh
2015-06-25 11:10 ` Sudip Mukherjee [this message]
2015-06-25 11:21 ` Dan Carpenter
2015-06-25 14:34 ` Ian Abbott
-- strict thread matches above, loose matches on Subject: below --
2015-06-25 11:13 Maninder Singh
2015-06-25 11:31 Maninder Singh
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=20150625111048.GA13366@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maninder1.s@samsung.com \
--cc=pankaj.m@samsung.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