From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Daniel Scally <djrscally@gmail.com>
Cc: yong.zhi@intel.com, sakari.ailus@linux.intel.com,
bingbu.cao@intel.com, tian.shu.qiu@intel.com, mchehab@kernel.org,
davem@davemloft.net, robh@kernel.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
jorhand@linux.microsoft.com, kitakar@gmail.com,
kieran.bingham@ideasonboard.com, dan.carpenter@oracle.com
Subject: Re: [RFC PATCH v2] Add functionality to ipu3-cio2 driver allowing software_node connections to sensors on platforms designed for Windows
Date: Thu, 1 Oct 2020 20:50:39 +0300 [thread overview]
Message-ID: <20201001175039.GL3956970@smile.fi.intel.com> (raw)
In-Reply-To: <20201001093326.6208-1-djrscally@gmail.com>
On Thu, Oct 01, 2020 at 10:33:26AM +0100, Daniel Scally wrote:
...
> This patch is dependent on another (which implements the software node graph
> family of functions):
>
> https://lore.kernel.org/linux-media/20200915232827.3416-1-djrscally@gmail.com/
More thoughts about the (future) series. Can you rather do a series of patches
to understand what is going on here. I see something like this:
patch 1. Add unregister_nodes_reverse()
2. Use above in test_printf.c
3. Add that graph support patch
4. Add T: to MAINTAINERS for IPU3-CIO2
5. Add this patch
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2020-10-01 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 9:33 [RFC PATCH v2] Add functionality to ipu3-cio2 driver allowing software_node connections to sensors on platforms designed for Windows Daniel Scally
2020-10-01 17:37 ` Andy Shevchenko
2020-10-08 21:51 ` Dan Scally
2020-10-09 12:44 ` Andy Shevchenko
2020-10-09 15:02 ` Dan Scally
2020-10-01 17:50 ` Andy Shevchenko [this message]
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=20201001175039.GL3956970@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jorhand@linux.microsoft.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=kitakar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tian.shu.qiu@intel.com \
--cc=yong.zhi@intel.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).