From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Antoniu Miclaus" <antoniu.miclaus@analog.com>,
"Andrew Ijano" <andrew.ijano@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andy Shevchenko" <andriy.shevchenko@intel.com>
Subject: Re: [PATCH next v2] iio: sca3000: simplify with spi_get_device_match_data()
Date: Tue, 24 Feb 2026 21:53:08 +0530 [thread overview]
Message-ID: <e1aa362e-e0b0-4a3d-bcc8-3277c95fb708@oracle.com> (raw)
In-Reply-To: <a85cc647-16ec-4b02-babf-0129e300a852@oracle.com>
Hi Jonathan,
On 20/02/26 17:15, Harshit Mogalapalli wrote:
>>
>> Applied to the testing branch of iio.git. There was quite
>> a bit of fuzz (line changes) but was all straight forward.
>>
>
> Oh, sorry for that. Maybe because these patches: https://
> lore.kernel.org/all/20260205195845.4e108117@jic23-huawei/ were not
> present ?
>
> I don't see them here: https://git.kernel.org/pub/scm/linux/kernel/git/
> jic23/iio.git/log/drivers/iio/accel/sca3000.c?h=testing , so asking.
>
> This patch might have applied cleaner with the above series applied.
ping on this. Sorry if this is being tracked.
the possible reason for line changes is that
https://lore.kernel.org/all/20260205195845.4e108117@jic23-huawei/
patches are not part of the branch here:
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/log/?h=testing
While working on new patches is the testing branch right branch to use ?
Thanks,
Harshit
prev parent reply other threads:[~2026-02-24 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 10:24 Harshit Mogalapalli
2026-02-20 10:51 ` Jonathan Cameron
2026-02-20 11:45 ` Harshit Mogalapalli
2026-02-24 16:23 ` Harshit Mogalapalli [this message]
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=e1aa362e-e0b0-4a3d-bcc8-3277c95fb708@oracle.com \
--to=harshit.m.mogalapalli@oracle.com \
--cc=andrew.ijano@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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®