From: Jonathan Cameron <jic23@kernel.org>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Colin King <colin.king@canonical.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Biju Das <biju.das.jz@bp.renesas.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] iio: adc: Fix -EBUSY timeout error return
Date: Sun, 29 Aug 2021 18:01:58 +0100 [thread overview]
Message-ID: <20210829180136.58a11601@jic23-huawei> (raw)
In-Reply-To: <CA+V-a8ugKC8z2=0usUca4eYFLTHEorxdtmdmbE5vXZDo_Ob5vA@mail.gmail.com>
On Thu, 19 Aug 2021 18:39:02 +0100
"Lad, Prabhakar" <prabhakar.csengg@gmail.com> wrote:
> On Thu, Aug 19, 2021 at 6:21 PM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> >
> > On Wed, Aug 18, 2021 at 6:51 PM Prabhakar Mahadev Lad
> > <prabhakar.mahadev-lad.rj@bp.renesas.com> wrote:
> >
> > > with the subject changed to above: Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> >
> Again with the above fixed:
> Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> > Always put your tags in a single tag per single line. This will allow
> > tools to catch them up automatically.
> >
> My bad, fixed that now.
Tweaked patch name as suggested and applied to the fixes-togreg branch of iio.git
Too late to sneak this in pre merge window, so I'll do it after rc1.
Thanks,
Jonathan
>
> Cheers,
> Prabhakar
prev parent reply other threads:[~2021-08-29 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 17:21 [PATCH][next] iio: adc: Fix -EBUSY timeout error return Colin King
2021-08-18 15:50 ` Prabhakar Mahadev Lad
2021-08-19 17:20 ` Andy Shevchenko
2021-08-19 17:39 ` Lad, Prabhakar
2021-08-29 17:01 ` Jonathan Cameron [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=20210829180136.58a11601@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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;
as well as URLs for NNTP newsgroup(s).