From: Quentin Deslandes <quentin.deslandes@itdev.co.uk>
To: "kernel-janitors@vger.kernel.org" <kernel-janitors@vger.kernel.org>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Quentin Deslandes <quentin.deslandes@itdev.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Cristian Sicilia <sicilia.cristian@gmail.com>
Subject: [PATCH 0/3] staging: axis-fifo: probe function cleanup
Date: Fri, 1 Nov 2019 21:42:46 +0000 [thread overview]
Message-ID: <20191101214232.16960-1-quentin.deslandes@itdev.co.uk> (raw)
Avoid parsing unused device tree properties and add a note on ignored /
unsupported properties inside the joined documentation instead.
Also use managed functions to claim the device's resources and remove unused
resource pointer from the device's internal structure.
Quentin Deslandes (3):
staging: axis-fifo: avoid parsing ignored device tree properties
staging: axis-fifo: request resources using managed functions
staging: axis-fifo: remove unused pointer to memory resource
drivers/staging/axis-fifo/axis-fifo.c | 301 +++++++-----------------
drivers/staging/axis-fifo/axis-fifo.txt | 18 +-
2 files changed, 90 insertions(+), 229 deletions(-)
--
2.23.0
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next reply other threads:[~2019-11-01 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 21:42 Quentin Deslandes [this message]
2019-11-01 21:42 ` [PATCH 1/3] staging: axis-fifo: avoid parsing ignored device tree properties Quentin Deslandes
2019-11-01 21:42 ` [PATCH 2/3] staging: axis-fifo: request resources using managed functions Quentin Deslandes
2019-11-01 21:42 ` [PATCH 3/3] staging: axis-fifo: remove unused pointer to memory resource Quentin Deslandes
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=20191101214232.16960-1-quentin.deslandes@itdev.co.uk \
--to=quentin.deslandes@itdev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sicilia.cristian@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).