From: Jonathan Cameron <jic23@kernel.org>
To: Abhash jha <abhashkumarjha123@gmail.com>
Cc: linux-iio@vger.kernel.org, anshulusr@gmail.com, lars@metafoo.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/2] Add light channel for LTR390
Date: Sun, 18 Aug 2024 17:05:35 +0100 [thread overview]
Message-ID: <20240818170535.7a1aa6b5@jic23-huawei> (raw)
In-Reply-To: <CAG=0RqJN=M5+w4CDXggDnoyOrW5qxTejJy=UkzMQX36emFT5fw@mail.gmail.com>
On Sat, 17 Aug 2024 23:07:37 +0530
Abhash jha <abhashkumarjha123@gmail.com> wrote:
> > I think I have. But with two versions of v7 I'm not 100% sure which one got picked
> > up. I've pushed out now as testing, so take a look.
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/log/?h=testing
> > >
> The two versions v7 patches are the same. I had sent the same thing
> again because
> I thought it might have gotten lost in your mail.
> My apologies for getting you confused.
Ah. Never bother doing that. Just send a 'ping' to the original
thread.
Most maintainers now use a lot of automation so tend not to drop messages
any more (it used to happen occasionally).
Also convention is to wait at least 2 weeks before pinging.
Jonathan
>
> Thanks,
> Abhash
next prev parent reply other threads:[~2024-08-18 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 11:31 [PATCH v7 0/2] Add light channel for LTR390 Abhash Jha
2024-08-14 11:31 ` [PATCH v7 1/2] iio: light: ltr390: Add ALS channel and support for gain and resolution Abhash Jha
2024-08-14 11:31 ` [PATCH v7 2/2] iio: light: ltr390: Calculate 'counts_per_uvi' dynamically Abhash Jha
2024-08-17 14:39 ` [PATCH v7 0/2] Add light channel for LTR390 Jonathan Cameron
2024-08-17 15:50 ` Abhash jha
2024-08-17 16:49 ` Jonathan Cameron
2024-08-17 17:37 ` Abhash jha
2024-08-18 16:05 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-04 14:23 Abhash Jha
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=20240818170535.7a1aa6b5@jic23-huawei \
--to=jic23@kernel.org \
--cc=abhashkumarjha123@gmail.com \
--cc=anshulusr@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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