From: Jakub Kicinski <kuba@kernel.org>
To: Thomas Fourier <fourier.thomas@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] ethernet: alt1: Fix missing DMA mapping tests
Date: Tue, 17 Jun 2025 14:54:40 -0700 [thread overview]
Message-ID: <20250617145440.0a055536@kernel.org> (raw)
In-Reply-To: <CA+eMeR2yEa4wsozLP94Zb2gQ67=xhC58PEdOKL8=RzaZotYhSQ@mail.gmail.com>
On Tue, 17 Jun 2025 17:47:50 +0200 Thomas Fourier wrote:
> On 16/06/2025 19:46, Jakub Kicinski wrote:
> > On Mon, 16 Jun 2025 15:59:55 +0200 Thomas Fourier wrote:
> >> According to Shuah Khan[1]
> > Sorry for a non-technical question -- are you part of some outreach /
> > training program? The presentation you linked is from 2013, I wonder
> > what made you pick up this particular task.
>
> I am doing a master thesis on static analysis and I am writing a checker
> with
I see.
> Smatch to test if error codes are well-checked. My supervisor suggested
> that
>
> I look at DMA mapping errors checks to see if people were interested in such
>
> patches and because they are quite easy to statically assert.
Given the community's mixed experience with researches, would you
be willing to share the name of the institution ?
next prev parent reply other threads:[~2025-06-17 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 15:05 [PATCH] (drivers/ethernet/atheros/atl1) test DMA mapping for error code Thomas Fourier
2025-06-12 17:24 ` Charalampos Mitrodimas
2025-06-13 1:32 ` Jakub Kicinski
2025-06-13 9:54 ` [PATCH v2] " Thomas Fourier
2025-06-13 14:43 ` Jakub Kicinski
2025-06-16 13:59 ` [PATCH net] ethernet: alt1: Fix missing DMA mapping tests Thomas Fourier
2025-06-16 17:46 ` Jakub Kicinski
2025-06-17 15:47 ` Thomas Fourier
2025-06-17 21:54 ` Jakub Kicinski [this message]
2025-06-17 21:59 ` Jakub Kicinski
2025-06-13 7:04 ` [PATCH] (drivers/ethernet/atheros/atl1) test DMA mapping for error code kernel test robot
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=20250617145440.0a055536@kernel.org \
--to=kuba@kernel.org \
--cc=fourier.thomas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®