linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Barnabás Pőcze" <pobrn@protonmail.com>
To: Coiby Xu <coiby.xu@gmail.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	Helmut Stult <helmut.stult@schinfo.de>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] HID: i2c-hid: add polling mode based on connected GPIO chip's pin status
Date: Mon, 19 Oct 2020 12:53:08 +0000	[thread overview]
Message-ID: <eA5pt2nxH5jB_qgxYEAHbUxK5Rxww6DE2IpvFKGrvMyZvM2nZbqil2egzmycszz06jij2B69JG-dqNQ5XLuufMzUm10bxLJ2xHoj9UEY5jk=@protonmail.com> (raw)
In-Reply-To: <20201019005412.rifxrvpdxu574jag@Rk>

> [...]
> You have been directly contributing to this patch because several
> improvements of next version are from you. I experienced a similar
> situation when submitting patches for QEMU. The only difference is
> that the feedbacks on the QEMU patches were also given in the format
> of patch. Or do you think a reviewed-by tag from you after you think
> the next version is of production quality is a better way to credit
> you?

Thanks, but there is no need for any tag from me. I am no maintainer/reviewer of/for
the affected subsystem.

> [...]


Regards,
Barnabás Pőcze

      reply	other threads:[~2020-10-19 12:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 13:13 [PATCH v2] HID: i2c-hid: add polling mode based on connected GPIO chip's pin status Coiby Xu
2020-10-16 15:00 ` Barnabás Pőcze
2020-10-17  0:45   ` Coiby Xu
2020-10-17 13:06     ` Barnabás Pőcze
2020-10-17 14:05       ` Coiby Xu
2020-10-17 14:58         ` Barnabás Pőcze
2020-10-18 12:23           ` Barnabás Pőcze
2020-10-19  0:54             ` Coiby Xu
2020-10-19  0:54           ` Coiby Xu
2020-10-19 12:53             ` Barnabás Pőcze [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='eA5pt2nxH5jB_qgxYEAHbUxK5Rxww6DE2IpvFKGrvMyZvM2nZbqil2egzmycszz06jij2B69JG-dqNQ5XLuufMzUm10bxLJ2xHoj9UEY5jk=@protonmail.com' \
    --to=pobrn@protonmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=coiby.xu@gmail.com \
    --cc=helmut.stult@schinfo.de \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).