From: Greg KH <gregkh@linuxfoundation.org>
To: Raag Jadav <raag.jadav@intel.com>
Cc: david.m.ertman@intel.com, ira.weiny@intel.com, lee@kernel.org,
andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, heikki.krogerus@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] driver core: auxiliary bus: Introduce auxiliary device resource management
Date: Wed, 14 May 2025 14:35:01 +0200 [thread overview]
Message-ID: <2025051433-fade-flirt-d3e0@gregkh> (raw)
In-Reply-To: <20250514122432.4019606-2-raag.jadav@intel.com>
On Wed, May 14, 2025 at 05:54:31PM +0530, Raag Jadav wrote:
> With more and more drivers adopting to auxiliary bus infrastructure comes
> the need for managing resources at auxiliary device level. This is useful
> for cases where parent device shares variable number and type of resources
> with auxiliary child device but doesn't require any active involvement in
> managing them.
>
> This reduces potential duplication of resource APIs that may be required by
> parent device driver. With this in place parent driver will be responsible
> for filling up respective resources and its count in auxiliary device
> structure before registering it, so that the leaf drivers can utilize in
> their probe function. Lifecycle of these resources will be as long as the
> auxiliary device exists.
>
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
> drivers/base/auxiliary.c | 145 ++++++++++++++++++++++++++++++++++
> include/linux/auxiliary_bus.h | 18 +++++
> 2 files changed, 163 insertions(+)
Sorry, but again, you are not following the required rules for Intel
kernel submissions for this subsystem. Please work with the Intel
kernel team to fix this up before you resend.
greg k-h
next prev parent reply other threads:[~2025-05-14 12:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 12:24 [PATCH v5 0/2] Auxiliary device support for MFD Raag Jadav
2025-05-14 12:24 ` [PATCH v5 1/2] driver core: auxiliary bus: Introduce auxiliary device resource management Raag Jadav
2025-05-14 12:35 ` Greg KH [this message]
2025-05-14 15:52 ` Raag Jadav
2025-05-14 12:36 ` Andy Shevchenko
2025-05-15 12:52 ` Raag Jadav
2025-05-15 13:06 ` Andy Shevchenko
2025-05-16 19:20 ` Raag Jadav
2025-05-19 10:44 ` Andy Shevchenko
2025-05-19 11:52 ` Raag Jadav
2025-05-14 15:27 ` kernel test robot
2025-05-14 15:58 ` kernel test robot
2025-05-14 12:24 ` [PATCH v5 2/2] mfd: core: Support auxiliary device Raag Jadav
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=2025051433-fade-flirt-d3e0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=david.m.ertman@intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=ira.weiny@intel.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=raag.jadav@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
all inboxes | Powered by JetHome®