lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHc1_P6m11M=1bP-0k_ndgtkLtfnkSCMScznCC+HnWWQ1XtGHw@mail.gmail.com>
Date: Tue, 30 Dec 2025 00:15:43 +0530
From: Shrikant <raskar.shree97@...il.com>
To: Jonathan Cameron <jic23@...nel.org>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org, 
	dlechner@...libre.com, nuno.sa@...log.com, andy@...nel.org, heiko@...ech.de, 
	neil.armstrong@...aro.org, skhan@...uxfoundation.org, 
	david.hunter.linux@...il.com, linux-iio@...r.kernel.org, 
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/4] iio: proximity: Add interrupt support for RFD77402

On Sat, Dec 27, 2025 at 11:16 PM Jonathan Cameron <jic23@...nel.org> wrote:
>
> On Sun, 21 Dec 2025 14:08:58 +0530
> Shrikant Raskar <raskar.shree97@...il.com> wrote:
>
> > This patch series adds:
> >  - Add RF Digital vendor prefix
> >  - YAML binding for RFD77402
> >  - Add OF device ID for enumeration via DT
> >  - Use kernel helper for result polling
> >  - Interrupt handling support
> >
> > These changes enable DT-based configuration and event-driven
> > operation for the RFD77402 Time-of-Flight sensor.
>
> Hi Shrikant,
>
> I'm only seeing this cover letter (and lore doesn't seem
> to have the patches either).  Probably need to resend them.
Hello Jonathan,
Apologies for the confusion. I have tried re-sending the patch
series multiple times, but each time only the cover letter is getting
delivered, while the individual patches do not seem to go through due
to Gmail's daily sending limit.I haven't fully resolved the issue yet,
but I'm trying to figure out a solution on my end. If you have
any suggestions or best practices to avoid such delivery issues, I
would really appreciate your guidance.

Sorry for the inconvenience, and thank you for your patience.
Regards,
Shrikant

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ