From: "Andreas Hindborg (Samsung)" <nmi@metaspace.dk>
To: Philipp Stanner <pstanner@redhat.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
rust-for-linux@vger.kernel.org
Subject: Re: RfL currently does not integrate very well with some Kconfigs
Date: Thu, 15 Feb 2024 18:29:32 +0100 [thread overview]
Message-ID: <87zfw1ocjp.fsf@metaspace.dk> (raw)
In-Reply-To: <CANiq72kQ52nMEhe_-_vxRjV0-BOBU6DbfYUni_SCEaAyrZjc5Q@mail.gmail.com>
Hi Philipp,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> writes:
> On Thu, Feb 15, 2024 at 4:24 PM Philipp Stanner <pstanner@redhat.com> wrote:
>>
>> Recently, I've been trying to accomplish some work on the rust-pci
>> branch in RfL.
>
> For the `rust-pci` branch, please create issues in GitHub, ask in
> Zulip and/or contact Andreas through Zulip like the website mentions.
> It is not code ready for upstreaming. Please see:
>
> https://rust-for-linux.com/branches#rust-pci
> https://github.com/Rust-for-Linux/linux/blob/rust-pci/README
>
>> So, it would seem there are some "deponds on" entries missing
>> somewhere.
>
> It sounds to me like there are missing `#[cfg(...)]`s in the code
> (i.e. conditional compilation), rather than missing `depends on`.
It is likely. The code is only tested with the NVMe driver. It is not
polished at all.
If you find an issue and fix it I would apply your patch to the rust-pci
branch. You can also send me error description and I will try to help
solve the issue. Email or Github issue is fine with me.
>> Is this problem known? Any plans or suggestions how to deal with it?
I am aware that there must be issues, but I am not aware of specific
issues. Again, patches or bug reports are welcome.
Best regards,
Andreas
next prev parent reply other threads:[~2024-02-15 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 15:21 RfL currently does not integrate very well with some Kconfigs Philipp Stanner
2024-02-15 16:22 ` Miguel Ojeda
2024-02-15 17:29 ` Andreas Hindborg (Samsung) [this message]
2024-02-16 19:25 ` Andreas Hindborg (Samsung)
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=87zfw1ocjp.fsf@metaspace.dk \
--to=nmi@metaspace.dk \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=pstanner@redhat.com \
--cc=rust-for-linux@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 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.