From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Syed Nayyar Waris <syednwaris@gmail.com>
Cc: William Breathitt Gray <vilhelm.gray@gmail.com>,
Jonathan Cameron <jic23@kernel.org>, <linux-iio@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 1/3] counter: 104-quad-8: Add lock guards - generic interface
Date: Mon, 8 Jun 2020 12:08:43 +0100 [thread overview]
Message-ID: <20200608120843.00007870@Huawei.com> (raw)
In-Reply-To: <CACG_h5qG7xU0kL1-Hn8q4S338ESAzz4qjN56Z8Bfi9ekYRTTzg@mail.gmail.com>
On Sun, 7 Jun 2020 11:00:53 +0530
Syed Nayyar Waris <syednwaris@gmail.com> wrote:
> On Sun, Jun 7, 2020 at 9:39 AM William Breathitt Gray
> <vilhelm.gray@gmail.com> wrote:
> >
> > On Sun, Jun 07, 2020 at 09:28:40AM +0530, Syed Nayyar Waris wrote:
> > > On Sat, Apr 4, 2020 at 7:36 PM Jonathan Cameron <jic23@kernel.org> wrote:
> > > >
> > > > On Mon, 30 Mar 2020 23:54:32 +0530
> > > > Syed Nayyar Waris <syednwaris@gmail.com> wrote:
> > > >
> > > > > Hi Jonathan
> > > > >
> > > > > >Looks good. I'm not sure right now which tree I'll take this through
> > > > > >(depends on whether it looks like we'll get an rc8 and hence I can sneak
> > > > > >it in for the coming merge window or not).
> > > > > >
> > > > > >So poke me if I seem to have forgotten to apply this in a week or so.
> > > > >
> > > > > Gentle Reminder.
> > > > > Thanks !
> > > > > Syed Nayyar Waris
> > > >
> > > > Thanks. I've applied it to the fixes-togreg branch of iio.git which will go
> > > > upstream after the merge window closes.
> > > >
> > > > Thanks,
> > > >
> > > > Jonathan
> > > >
> > >
> > > HI Jonathan,
> > >
> > > I think only the patch [1/3] has been applied. Patches [2/3] and [3/3] have not.
> > >
> > > The three patches were:
> > > https://lore.kernel.org/patchwork/patch/1210135/
> > > https://lore.kernel.org/patchwork/patch/1210136/
> > > https://lore.kernel.org/patchwork/patch/1210137/
> > >
> > > The last 2 patches need to be applied, I think.
> > >
> > > Regards
> > > Syed Nayyar Waris
> >
> > Just a heads-up: the relevant bugs are present in the 5.7 release so it
> > would be prudent to tag those two patches with respective Fixes lines.
> >
> > William Breathitt Gray
>
> Mentioning below, the 'Fixes' tags just for reference:
> For patch [2/3]: counter: 104-quad-8: Add lock guards - differential encoder.
> Fixes: bbef69e088c3 ("counter: 104-quad-8: Support Differential
> Encoder Cable Status")
>
> For patch [3/3]: counter: 104-quad-8: Add lock guards - filter clock prescaler.
> Fixes: 9b74dddf79be ("counter: 104-quad-8: Support Filter Clock Prescaler")
>
> I have replied on the v5 patches [2/3] and [3/3] with the (above)
> 'Fixes' tags. I have added the tags in the message.
>
> I think that was what you meant.
>
Gah. I lost them. I feel slightly less guilty though because they aren't
all in a thread so are scattered randomly in my email.
Please keep a given version of a patch set in a single thread. git will
do this by default unless you've specifically told it not to...
Ideally always use a cover letter as well except for single patch patch sets.
I'll sort these next time I'm on the right computer.
Jonathan
> Regards
> Syed Nayyar Waris
prev parent reply other threads:[~2020-06-08 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 12:49 [PATCH v5 1/3] counter: 104-quad-8: Add lock guards - generic interface Syed Nayyar Waris
2020-03-18 2:14 ` William Breathitt Gray
2020-03-22 17:58 ` Jonathan Cameron
2020-03-30 18:24 ` Syed Nayyar Waris
2020-04-04 14:06 ` Jonathan Cameron
2020-06-07 3:58 ` Syed Nayyar Waris
2020-06-07 4:09 ` William Breathitt Gray
2020-06-07 5:30 ` Syed Nayyar Waris
2020-06-08 11:08 ` 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=20200608120843.00007870@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syednwaris@gmail.com \
--cc=vilhelm.gray@gmail.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).