mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Beleswar Padhi <b-padhi@ti.com>
Cc: <kristo@kernel.org>, <ssantosh@kernel.org>, <afd@ti.com>,
	<vigneshr@ti.com>, <u-kumar1@ti.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 16/22] firmware: ti_sci: Move the huge ti_sci file into its own directory
Date: Fri, 20 Nov 2026 07:42:56 -0600	[thread overview]
Message-ID: <20261120134256.kb657juxyw2t3dva@ripple> (raw)
In-Reply-To: <20261029181147.266771-17-b-padhi@ti.com>

On 23:41-20261029, Beleswar Padhi wrote:
> From: Andrew Davis <afd@ti.com>
> 
> Move the huge ti_sci.c file and its header into its own "ti"
> sub-directory. While at it, rename the file to ti_sci_core.c as this
> file will be broken down into smaller files tied to operations as part
> of future cleanups.
> 
> Signed-off-by: Andrew Davis <afd@ti.com>
> Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
> ---


This patch conflicts with v7.4-rc2 as below -> could you rebase the series to
latest linux-next or v7.4-rc2?

0af298e62e5c treewide: refresh kmalloc_obj() conversions
4dd10fbbeb9c treewide: Convert devm_kmalloc() family to the devm_kmalloc_obj() family

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource

  reply	other threads:[~2026-11-20 13:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 18:11 [PATCH v3 00/22] Cleanup and Refactor TI-SCI driver Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 01/22] firmware: ti_sci: Move error message handling into ti_sci_get_one_xfer() Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 02/22] firmware: ti_sci: Move error message handling into ti_sci_do_xfer() Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 03/22] firmware: ti_sci: Move check for ACK " Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 04/22] firmware: ti_sci: Remove out of place RM debug messages Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 05/22] firmware: ti_sci: Name response variable resp for consistency Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 06/22] firmware: ti_sci: Handle xfer cleanup inside ti_sci_do_xfer() Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 07/22] firmware: ti_sci: Pass request struct into ti_sci_do_xfer() Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 08/22] firmware: ti_sci: Combine xfer allocation and transfer functions Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 09/22] firmware: ti_sci: Fetch info struct from handle inside ti_sci_do_xfer() Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 10/22] firmware: ti_sci: Use tx_message as message buffer directly Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 11/22] firmware: ti_sci: Use rx_message as message receive buffer Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 12/22] firmware: ti_sci: Fix some kernel-doc references in structs Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 13/22] soc: ti: ti_sci_protocol.h: Add missing documentation for structs Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 14/22] firmware: ti_sci: Do not export reboot control Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 15/22] firmware: ti_sci: Use pmops fxn pointers in suspend/resume hooks Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 16/22] firmware: ti_sci: Move the huge ti_sci file into its own directory Beleswar Padhi
2026-11-20 13:42   ` Nishanth Menon [this message]
2026-10-29 18:11 ` [PATCH v3 17/22] firmware: ti: ti_sci: Add missing includes for self-contained headers Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 18/22] firmware: ti: ti_sci_device: Move device ops into its own file Beleswar Padhi
2026-11-20 13:56   ` Nishanth Menon
2026-10-29 18:11 ` [PATCH v3 19/22] firmware: ti: ti_sci_clock: Move clock " Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 20/22] firmware: ti: ti_sci_pm: Move pm " Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 21/22] firmware: ti: ti_sci_rm: Move rm " Beleswar Padhi
2026-10-29 18:11 ` [PATCH v3 22/22] firmware: ti: ti_sci_proc: Move processor " Beleswar Padhi

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=20261120134256.kb657juxyw2t3dva@ripple \
    --to=nm@ti.com \
    --cc=afd@ti.com \
    --cc=b-padhi@ti.com \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ssantosh@kernel.org \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.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®