From: Ivan Orlov <ivan.orlov0322@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: perex@perex.cz, tiwai@suse.com, corbet@lwn.net,
alsa-devel@alsa-project.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] ALSA: Add new driver for Marian M2 sound card
Date: Tue, 19 Sep 2023 21:23:46 +0400 [thread overview]
Message-ID: <5e729667-f08b-d358-eff7-65c5d88e4352@gmail.com> (raw)
In-Reply-To: <2023091917-zippy-alienate-3efc@gregkh>
On 9/19/23 12:53, Greg KH wrote:
> On Tue, Sep 19, 2023 at 12:46:34PM +0400, Ivan Orlov wrote:
>> By the way, is there any way to detect such issues automatically? I've seen
>> that the kernel test robot detects a lot of similar stuff, perhaps there is
>> any tools/linters which can be set up locally?
>
> Not that I know of, sorry, I rely on the kernel test robot for lots of
> these things :)
>
> But, the robot is running all open tests, so dig into the public repo of
> it to see what it is using and perhaps run those tests locally? Lots of
> them are just different build options and running sparse.
>
Alright, I will take a look on the sources. Thank you for the advice! :)
next prev parent reply other threads:[~2023-09-21 13:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 18:10 [PATCH v2 1/2] ALSA: docs: Add Marian M2 driver documentation Ivan Orlov
2023-09-18 18:10 ` [PATCH v2 2/2] ALSA: Add new driver for Marian M2 sound card Ivan Orlov
2023-09-19 3:41 ` kernel test robot
2023-09-19 7:56 ` Takashi Iwai
2023-09-19 8:35 ` Ivan Orlov
2023-09-19 8:04 ` Greg KH
2023-09-19 8:46 ` Ivan Orlov
2023-09-19 8:53 ` Greg KH
2023-09-19 17:23 ` Ivan Orlov [this message]
2023-11-05 20:44 ` kernel test robot
2023-09-19 7:57 ` [PATCH v2 1/2] ALSA: docs: Add Marian M2 driver documentation Jonathan Corbet
2023-09-19 8:49 ` Ivan Orlov
2023-09-19 8:03 ` Greg KH
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=5e729667-f08b-d358-eff7-65c5d88e4352@gmail.com \
--to=ivan.orlov0322@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--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 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).