DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: ci@dpdk.org, adham@nvidia.com
Subject: Re: Adding WinOF drivers to Windows Server 2022 machine at the DPDK Community Lab
Date: Sun, 15 Sep 2024 19:09:53 -0400	[thread overview]
Message-ID: <CAJvnSUCbTRVyiEFko6PnbeVOakiE4wfdDCCynDDNTHznBQP0wA@mail.gmail.com> (raw)
In-Reply-To: <20240912060512.GF6879@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>

Thanks. I posted an update but basically yes the build now works for
mlx5 drivers on clang/llvm: https://bugs.dpdk.org/show_bug.cgi?id=1532

Thanks Adham and Tyler.

On Thu, Sep 12, 2024 at 2:05 AM Tyler Retzlaff
<roretzla@linux.microsoft.com> wrote:
>
> Hi Patrick,
>
> sorry for the late reply. i see no problem with having winof-2 drivers
> on the system. i imagine on clang/llvm builds this will cause the mlx5
> drivers to be built.
>
> ty
>
> On Tue, Sep 10, 2024 at 03:48:23PM -0400, Patrick Robb wrote:
> > Hi Tyler,
> >
> > I would like to add WinOF drivers to our Windows server 2022 machine,
> > per this ticket which came in:
> > https://bugs.dpdk.org/show_bug.cgi?id=1532
> >
> > Figured I'd just give you a day or so to comment in case you had any
> > view, otherwise if I don't hear from you I'll make this change
> > tomorrow! Cheers.
> >
> > --
> > Patrick Robb
> >
> > Technical Service Manager
> >
> > UNH InterOperability Laboratory
> >
> > 21 Madbury Rd, Suite 100, Durham, NH 03824
> >
> > www.iol.unh.edu

      reply	other threads:[~2024-09-15 23:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10 19:48 Patrick Robb
2024-09-12  6:05 ` Tyler Retzlaff
2024-09-15 23:09   ` Patrick Robb [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=CAJvnSUCbTRVyiEFko6PnbeVOakiE4wfdDCCynDDNTHznBQP0wA@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=adham@nvidia.com \
    --cc=ci@dpdk.org \
    --cc=roretzla@linux.microsoft.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).