All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Igor Prusov <ivprusov@salutedevices.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Philipp Zabel <p.zabel@pengutronix.de>
Cc: prusovigor@gmail.com, kernel@salutedevices.com,
	linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/6] dt-bindings: vendor-prefixes: Add NeoFidelity, Inc
Date: Fri, 12 Jul 2024 09:55:47 +0200	[thread overview]
Message-ID: <c59fc09d-e178-4acd-a825-4f00978c167e@kernel.org> (raw)
In-Reply-To: <20240709221203.92167-2-ivprusov@salutedevices.com>

On 10/07/2024 00:11, Igor Prusov wrote:
> Add vendor prefix for NeoFidelity, Inc
> 
> Signed-off-by: Igor Prusov <ivprusov@salutedevices.com>

Did you just ignored every response?


<form letter>
This is a friendly reminder during the review process.

It looks like you received a tag and forgot to add it.

If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new
versions, under or above your Signed-off-by tag. Tag is "received", when
provided in a message replied to you on the mailing list. Tools like b4
can help here. However, there's no need to repost patches *only* to add
the tags. The upstream maintainer will do that for tags received on the
version they apply.

https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577

If a tag was not added on purpose, please state why and what changed.
</form letter>

Best regards,
Krzysztof


  reply	other threads:[~2024-07-12  7:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 22:11 [PATCH v2 0/6] ASoC: Add NTP8918 and NTP8835 codecs support Igor Prusov
2024-07-09 22:11 ` [PATCH v2 1/6] dt-bindings: vendor-prefixes: Add NeoFidelity, Inc Igor Prusov
2024-07-12  7:55   ` Krzysztof Kozlowski [this message]
2024-07-12 21:30     ` Igor Prusov
2024-07-09 22:11 ` [PATCH v2 2/6] ASoC: codecs: Add NeoFidelity Firmware helpers Igor Prusov
2024-07-09 22:12 ` [PATCH v2 3/6] ASoC: dt-bindings: Add bindings for NeoFidelity NTP8918 Igor Prusov
2024-07-12  7:56   ` Krzysztof Kozlowski
2024-07-09 22:12 ` [PATCH v2 4/6] ASoC: codecs: Add NeoFidelity NTP8918 codec Igor Prusov
2024-07-09 22:12 ` [PATCH v2 5/6] ASoC: dt-bindings: Add bindings for NeoFidelity NTP8835 Igor Prusov
2024-07-12  7:56   ` Krzysztof Kozlowski
2024-07-09 22:12 ` [PATCH v2 6/6] ASoC: codecs: Add NeoFidelity NTP8835 codec Igor Prusov
2024-07-11 21:10 ` [PATCH v2 0/6] ASoC: Add NTP8918 and NTP8835 codecs support Rob Herring
2024-07-12 21:43   ` Igor Prusov

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=c59fc09d-e178-4acd-a825-4f00978c167e@kernel.org \
    --to=krzk@kernel.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ivprusov@salutedevices.com \
    --cc=kernel@salutedevices.com \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=perex@perex.cz \
    --cc=prusovigor@gmail.com \
    --cc=robh@kernel.org \
    --cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.