linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manuel Traut <manuel.traut@mt.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Frieder Schrempf <frieder.schrempf@kontron.de>,
	linux-input@vger.kernel.org
Subject: Re: EXTERNAL - [PATCH 2/3 v6] input: pwm-beeper: add feature to set volume level
Date: Tue, 24 Jan 2023 17:11:49 +0100	[thread overview]
Message-ID: <Y9ADRd+WbGeJhSoZ@mt.com> (raw)
In-Reply-To: <907da24c-1619-a75b-b6b6-66c8ae86df6d@kernel.org>

Hi Krzysztof,

Am 24.01.2023 um 12:29 hat Krzysztof Kozlowski geschrieben:
> On 24/01/2023 12:13, Manuel Traut wrote:
> > This patch adds the documentation for the devicetree bindings to set
> > the volume levels.
> > 
> > Signed-off-by: Frieder Schrempf <frieder.schrempf@exceet.de>
> > Acked-by: Rob Herring <robh@kernel.org>
> > ---
> 
> One more:
> 
> Use subject prefixes matching the subsystem (which you can get for
> example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
> your patch is touching).

Thanks for your feedback. I will post a v7 soon that includes your
feedback, the findings from the kernelbot and a fix that allows
unloading and loading of the module.

Best regards
Manuel

  reply	other threads:[~2023-01-24 16:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 11:11 [PATCH 0/3 v6] input: pwm-beeper: add feature to set volume level Manuel Traut
2023-01-24 11:12 ` [PATCH 1/3 " Manuel Traut
2023-01-24 13:18   ` kernel test robot
2023-01-24 14:40   ` kernel test robot
2023-01-24 11:13 ` [PATCH 2/3 " Manuel Traut
2023-01-24 11:29   ` Krzysztof Kozlowski
2023-01-24 11:29   ` Krzysztof Kozlowski
2023-01-24 16:11     ` Manuel Traut [this message]
2023-01-24 11:14 ` [PATCH 3/3 " Manuel Traut

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=Y9ADRd+WbGeJhSoZ@mt.com \
    --to=manuel.traut@mt.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=frieder.schrempf@kontron.de \
    --cc=krzk@kernel.org \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).