From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
linux-iio@vger.kernel.org, Felipe Balbi <balbi@kernel.org>,
Raymond Tan <raymond.tan@intel.com>
Subject: Re: [PATCH v3] counter: Add support for Intel Quadrature Encoder Peripheral
Date: Wed, 2 Jun 2021 23:38:58 +0900 [thread overview]
Message-ID: <YLeYAiKHHjk6Ucv8@shinobu> (raw)
In-Reply-To: <20210602153706.00003bbc@Huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2403 bytes --]
On Wed, Jun 02, 2021 at 03:37:06PM +0100, Jonathan Cameron wrote:
> On Wed, 2 Jun 2021 23:23:44 +0900
> William Breathitt Gray <vilhelm.gray@gmail.com> wrote:
>
> > On Wed, Jun 02, 2021 at 02:41:29PM +0300, Jarkko Nikula wrote:
> > > Hi
> > >
> > > On 6/2/21 7:03 AM, William Breathitt Gray wrote:
> > > > On Thu, May 27, 2021 at 04:58:38PM +0300, Jarkko Nikula wrote:
> > > >> Documentation/ABI/testing/sysfs-bus-counter | 9 +
> > > >> drivers/counter/Kconfig | 10 +
> > > >> drivers/counter/Makefile | 1 +
> > > >> drivers/counter/intel-qep.c | 546 ++++++++++++++++++++
> > > >> 4 files changed, 566 insertions(+)
> > > >> create mode 100644 drivers/counter/intel-qep.c
> > > >
> > > > Hi Jarkko,
> > > >
> > > > I noticed the intel-qep.c file is missing an entry in the MAINTAINERS
> > > > file. Would you be able to resubmit this patch with a proper entry added
> > > > to MAINTAINERS so that users have the relevant contact info to reach the
> > > > maintainers of this driver? You can keep my Signed-off tag on as well so
> > > > that we know the code has already been reviewed.
> > > >
> > > Ah, added now. I sent the update and didn't dare to add your signature
> > > due the sidenote below :-)
> > >
> > > Sidenote, to my understanding Signed-off-by requires patch went through
> > > that person and Acked-by is used when maintainer accepts the patch but
> > > another person commits it with his/her Signed-off-by.
> > >
> > > Jarkko
> >
> > Is that so? I'm not really sure myself of the particular nuances -- I
> > wonder if there's an explanation somewhere in the Documentation files,
> > or if someone else can explain it more in-depth. Regardless you've made
> > all the changes I've requested so here's my Ack for your troubles. :-)
> There is quite a it in https://www.kernel.org/doc/html/latest/process/submitting-patches.html
>
> >
> > Acked-by: William Breathitt Gray <vilhelm.gray@gmail.com>
> >
>
> Reviewed-by also fine for this case given I know you are the maintainer
> and will only give that if happy. Exactly what the meaning of
> Acked-by / Reviewed-by when given by a maintainer is a question that
> has been hotly debated a few times in the past.
>
> Jonathan
Thanks for clearing that up for me!
William Breathitt Gray
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-06-02 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 13:58 [PATCH v3] counter: Add support for Intel Quadrature Encoder Peripheral Jarkko Nikula
2021-05-28 4:28 ` William Breathitt Gray
2021-06-02 4:03 ` William Breathitt Gray
2021-06-02 11:41 ` Jarkko Nikula
2021-06-02 14:23 ` William Breathitt Gray
2021-06-02 14:37 ` Jonathan Cameron
2021-06-02 14:38 ` William Breathitt Gray [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=YLeYAiKHHjk6Ucv8@shinobu \
--to=vilhelm.gray@gmail.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=balbi@kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-iio@vger.kernel.org \
--cc=raymond.tan@intel.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