mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Murali Krishna <muralikrishna2444b@gmail.com>
To: srini@kernel.org
Cc: ekansh.gupta@oss.qualcomm.com, gregkh@linuxfoundation.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Murali Krishna <muralikrishna2444b@gmail.com>
Subject: misc: fastrpc: is a ctx_idr IDR -> XArray conversion wanted?
Date: Wed, 23 Sep 2026 13:52:05 +0530	[thread overview]
Message-ID: <20260923082254.15312-1-muralikrishna2444b@gmail.com> (raw)

Hi Srini, Ekansh,

I am new to kernel development and would like to start contributing. I
do not have much experience yet, but I am willing to learn and to put in
the work properly.

Documentation/core-api/idr.rst states that the IDR interface is
deprecated in favour of the XArray, and fastrpc's ctx_idr is still an
IDR. I have a conversion prepared -- XA_FLAGS_ALLOC1, xa_alloc_cyclic()
with the cursor kept in struct fastrpc_channel_ctx, xa_load() and
xa_erase(), and cctx->lock left as it is -- with no intended functional
change.

Before posting it, I would rather ask than take up your review time: is
such a conversion wanted in fastrpc, or is the IDR usage here fine as it
is? I have seen similar conversions in other subsystems declined as
unnecessary, so I did not want to assume.

I should also say that it is build- and sparse-tested only (x86_64,
COMPILE_TEST, W=1 C=1, no new warnings). I have no Qualcomm hardware, so
the converted path has never actually run.

I am aware of the accel/qda series, described as an alternative to this
driver. If fastrpc.c is effectively in maintenance mode, that is a good
reason to say no.

If the answer is no, I would be grateful if you could point me towards
something you would actually like to see worked on here. I am happy to
start with something small and learn from the review.

Thank you for your time,
Murali Krishna

             reply	other threads:[~2026-09-23  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23  8:22 Murali Krishna [this message]
2026-09-23  9:28 ` Greg KH
2026-09-23  9:40   ` Murali Krishna
2026-09-23 10:41     ` Greg KH

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=20260923082254.15312-1-muralikrishna2444b@gmail.com \
    --to=muralikrishna2444b@gmail.com \
    --cc=ekansh.gupta@oss.qualcomm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srini@kernel.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 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®