Re: [PATCH 3/3] rust: upgrade to Rust 1.73.0

2023-10-09 Thread Vincenzo Palazzo
> The vast majority of changes are due to our `alloc` fork being upgraded > at once. Ah this is annoying sometimes :/ > > There are two kinds of changes to be aware of: the ones coming from > upstream, which we should follow as closely as possible, and the updates > needed in our added fallible A

Re: [PATCH] docs: submitting-patches: Introduce Test: tag

2023-10-09 Thread Konrad Dybcio
On 8.10.2023 19:18, Geert Uytterhoeven wrote: > On Sat, Oct 7, 2023 at 2:57 PM Jonathan Corbet wrote: >> Konrad Dybcio writes: >> >>> Currently, we blindly trust the submitters that they both compiled their >>> code at all, tested it on a relevant device, and have done so in a manner >>> that mad

Re: [REBASE PATCH v5 10/17] pstore: Add pstore_region_defined() helper and export it

2023-10-09 Thread Mukesh Ojha
Thanks for the review. On 9/14/2023 4:54 AM, Kees Cook wrote: On Mon, Sep 11, 2023 at 04:23:52PM +0530, Mukesh Ojha wrote: There are users like Qualcomm minidump which is interested in knowing the pstore frontend addresses and sizes from the backend (ram) to be able to register it with firmware

[PATCH net-next] docs: try to encourage (netdev?) reviewers

2023-10-09 Thread Jakub Kicinski
Add a section to netdev maintainer doc encouraging reviewers to chime in on the mailing list. The questions about "when is it okay to share feedback" keep coming up (most recently at netconf) and the answer is "pretty much always". Extend the section of 7.AdvancedTopics.rst which deals with revie