All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: <linux-arm-kernel@lists.infradead.org>
Cc: Cristian Marussi <cristian.marussi@arm.com>
Subject: Re: [PATCH 0/3] firmware: arm_scmi: Minor cleanups in the scmi bus layer
Date: Wed, 12 Mar 2025 11:20:41 +0000	[thread overview]
Message-ID: <Z9FuCUAzjd4y6oEL@bogus> (raw)
In-Reply-To: <20250312-b4-scmi_minor_cleanup-v1-0-51a514282794@arm.com>

On Wed, Mar 12, 2025 at 11:14:31AM +0000, Sudeep Holla wrote:
> These cleanup centralizes error logging for SCMI device creation into a
> single helper function, _scmi_device_create(), consolidates the device
> matching logic into a single function, and ensures that devices must
> have a name for registration, removing support for unnamed devices while
> matching the devices and drivers for probing.
> 

Please ignore this as I messed by and somehow managed to not include
arm-scmi list with wrong usage of b4 send, will resend soon.

-- 
Regards,
Sudeep


  parent reply	other threads:[~2025-03-12 11:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 11:14 [PATCH 0/3] firmware: arm_scmi: Minor cleanups in the scmi bus layer Sudeep Holla
2025-03-12 11:14 ` [PATCH 1/3] firmware: arm_scmi: Ensure scmi_devices are always matched by name as well Sudeep Holla
2025-03-12 11:14 ` [PATCH 2/3] firmware: arm_scmi: Refactor device matching logic to eliminate duplication Sudeep Holla
2025-03-12 11:14 ` [PATCH 3/3] firmware: arm_scmi: Refactor error logging from SCMI device creation to single helper Sudeep Holla
2025-03-12 11:20 ` Sudeep Holla [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-12 11:40 [PATCH 0/3] firmware: arm_scmi: Minor cleanups in the scmi bus layer Sudeep Holla

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=Z9FuCUAzjd4y6oEL@bogus \
    --to=sudeep.holla@arm.com \
    --cc=cristian.marussi@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.