From: Dan Carpenter <dan.carpenter@oracle.com>
To: Anton Vasilyev <vasilyev@ispras.ru>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
devel@driverdev.osuosl.org, ldv-project@linuxtesting.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johannes Thumshirn <jthumshirn@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sinan Kaya <okaya@codeaurora.org>, Hannes Reinecke <hare@suse.de>,
Gaurav Pathak <gauravpathak129@gmail.com>
Subject: Re: [PATCH v5] staging: rts5208: add error handling into rtsx_probe
Date: Wed, 1 Aug 2018 17:52:45 +0300 [thread overview]
Message-ID: <20180801145245.rkuvugnxm4fofauz@mwanda> (raw)
In-Reply-To: <cac7e1d3-dc55-5857-5fe5-4ff5bc39f2d1@ispras.ru>
On Wed, Aug 01, 2018 at 05:08:48PM +0300, Anton Vasilyev wrote:
> I found that staging-next already contains my patch v3, committed by Greg
> Kroah-Hartman.
>
> Do I need to send a new patch with a label renaming based on Dan Carpenter
> comments?
I had to look to see what I had said earlier... The naming isn't really
a problem but we should call scsi_host_put(host); if the
"dev->chip = kzalloc(sizeof(*dev->chip), GFP_KERNEL);" allocation fails.
regards,
dan capenter
next prev parent reply other threads:[~2018-08-01 14:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-09 16:38 [PATCH] staging: rts5208: add check on NULL before dereference Anton Vasilyev
2018-06-09 16:58 ` okaya
2018-06-09 19:34 ` Andy Shevchenko
2018-06-09 22:22 ` okaya
2018-06-12 13:06 ` Dan Carpenter
2018-06-13 16:55 ` [PATCH v2] " Anton Vasilyev
2018-06-13 17:00 ` Andy Shevchenko
2018-06-13 17:34 ` [PATCH v3] staging: rts5208: add error handling into rtsx_probe Anton Vasilyev
[not found] ` <20180613173128.32384-1-vasilyev@ispras.ru>
2018-06-19 7:42 ` your mail Dan Carpenter
2018-06-19 15:25 ` [PATCH v4] staging: rts5208: add error handling into rtsx_probe Anton Vasilyev
2018-06-19 17:13 ` Andy Shevchenko
2018-08-01 11:55 ` [PATCH v5] " Anton Vasilyev
2018-08-01 12:18 ` Andy Shevchenko
2018-08-01 14:08 ` Anton Vasilyev
2018-08-01 14:52 ` Dan Carpenter [this message]
2018-08-01 15:37 ` Andy Shevchenko
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=20180801145245.rkuvugnxm4fofauz@mwanda \
--to=dan.carpenter@oracle.com \
--cc=andy.shevchenko@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gauravpathak129@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=jthumshirn@suse.de \
--cc=ldv-project@linuxtesting.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okaya@codeaurora.org \
--cc=vasilyev@ispras.ru \
/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
all inboxes | Powered by JetHome®