From: Sven Van Asbroeck <thesven73@gmail.com>
To: hariprasad Kelam <hariprasad.kelam@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: fieldbus: make use of devm_platform_ioremap_resource
Date: Mon, 28 Oct 2019 17:11:26 -0400 [thread overview]
Message-ID: <CAGngYiXxagQMiHA-pZupTPHfyFz4kU=QOrvM28L_jSV1VGw=jQ@mail.gmail.com> (raw)
In-Reply-To: <CAGngYiX0zoAQB=SEoXfoMm9u_JzHu3eLErj4zmTYtSAoDwkp6Q@mail.gmail.com>
Hi Greg, friendly reminder... Did you miss the patch review below, or
is there a reason
why this isn't getting queued?
There seems to be a crowd chasing down this type of warnings, resulting
in multiple duplicates.
On Tue, Oct 8, 2019 at 9:31 AM Sven Van Asbroeck <thesven73@gmail.com> wrote:
>
> On Tue, Oct 8, 2019 at 2:11 AM hariprasad Kelam
> <hariprasad.kelam@gmail.com> wrote:
> >
> > From: Hariprasad Kelam <hariprasad.kelam@gmail.com>
> >
> > fix below issues reported by coccicheck
> > drivers/staging//fieldbus/anybuss/arcx-anybus.c:135:1-5: WARNING: Use
> > devm_platform_ioremap_resource for base
> > drivers/staging//fieldbus/anybuss/arcx-anybus.c:248:1-14: WARNING: Use
> > devm_platform_ioremap_resource for cd -> cpld_base
> >
> > Signed-off-by: Hariprasad Kelam <hariprasad.kelam@gmail.com>
> > ---
> > drivers/staging/fieldbus/anybuss/arcx-anybus.c | 8 ++------
> > 1 file changed, 2 insertions(+), 6 deletions(-)
>
> Reviewed-by: Sven Van Asbroeck <TheSven73@gmail.com>
> Tested-by: Sven Van Asbroeck <TheSven73@gmail.com>
next prev parent reply other threads:[~2019-10-28 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1570515056-23589-1-git-send-email-hariprasad.kelam@gmail.com>
2019-10-08 13:31 ` [PATCH] staging: fieldbus: make use of devm_platform_ioremap_resource Sven Van Asbroeck
2019-10-28 21:11 ` Sven Van Asbroeck [this message]
2019-10-29 8:03 ` Greg Kroah-Hartman
2019-10-29 13:05 ` Sven Van Asbroeck
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='CAGngYiXxagQMiHA-pZupTPHfyFz4kU=QOrvM28L_jSV1VGw=jQ@mail.gmail.com' \
--to=thesven73@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hariprasad.kelam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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).