From: Stefan Wahren <stefan.wahren@i2se.com>
To: Ojaswin Mujoo <ojaswin98@gmail.com>, nsaenz@kernel.org
Cc: gregkh@linuxfoundation.org, arnd@arndb.de,
dan.carpenter@oracle.com, phil@raspberrypi.com,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] staging: vchiq: Refactor vchiq cdev code
Date: Sun, 11 Jul 2021 12:33:54 +0200 [thread overview]
Message-ID: <99d116a6-b50b-6a56-e012-68388536ef53@i2se.com> (raw)
In-Reply-To: <84a14939b25b5babed921f7d2bad2975d8639fd3.1625401927.git.ojaswin98@gmail.com>
Am 04.07.21 um 17:57 schrieb Ojaswin Mujoo:
> Move the vchiq cdev initialization code to its own function for better
> code organization. Call the initialization function during probe, thus
> shifting the whole cdev creation logic (which was earlier split in
> vchiq_probe() and vchiq_driver_init()) to vchiq_probe().
>
> Signed-off-by: Ojaswin Mujoo <ojaswin98@gmail.com>
Reviewed-by: Stefan Wahren <stefan.wahren@i2se.com>
next prev parent reply other threads:[~2021-07-11 10:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 15:56 [PATCH v3 0/5] vchiq: Patch to separate platform and cdev code Ojaswin Mujoo
2021-07-04 15:57 ` [PATCH v3 1/5] staging: vchiq: Refactor vchiq " Ojaswin Mujoo
2021-07-11 10:33 ` Stefan Wahren [this message]
2021-07-04 15:57 ` [PATCH v3 2/5] staging: vchiq: Move certain declarations to vchiq_arm.h Ojaswin Mujoo
2021-07-11 10:34 ` Stefan Wahren
2021-07-04 15:58 ` [PATCH v3 3/5] staging: vchiq: Move vchiq char driver to its own file Ojaswin Mujoo
2021-07-05 9:56 ` Dan Carpenter
2021-07-05 10:58 ` Ojaswin Mujoo
2021-07-05 11:19 ` Dan Carpenter
2021-07-05 11:24 ` Ojaswin Mujoo
2021-07-11 10:35 ` Stefan Wahren
2021-07-04 15:59 ` [PATCH v3 4/5] staging: vchiq: Make creation of vchiq cdev optional Ojaswin Mujoo
2021-07-11 10:39 ` Stefan Wahren
2021-07-04 15:59 ` [PATCH v3 5/5] staging: vchiq: Combine vchiq platform code into single file Ojaswin Mujoo
2021-07-04 18:07 ` kernel test robot
2021-07-11 10:49 ` Stefan Wahren
2021-07-11 11:28 ` Ojaswin Mujoo
2021-07-21 8:22 ` Greg KH
2021-07-21 16:28 ` Ojaswin Mujoo
2021-07-11 10:29 ` [PATCH v3 0/5] vchiq: Patch to separate platform and cdev code Stefan Wahren
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=99d116a6-b50b-6a56-e012-68388536ef53@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nsaenz@kernel.org \
--cc=ojaswin98@gmail.com \
--cc=phil@raspberrypi.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).