Home
last modified time | relevance | path

Searched refs:crate (Results 1 – 18 of 18) sorted by relevance

/linux/drivers/clk/x86/
H A Dclk-cgu-pll.c28 u64 crate, frate, rate64; in lgm_pll_calc_rate() local
31 crate = rate64 * mult; in lgm_pll_calc_rate()
34 crate += frate; in lgm_pll_calc_rate()
35 do_div(crate, div); in lgm_pll_calc_rate()
37 return crate; in lgm_pll_calc_rate()
/linux/scripts/
H A Dgenerate_rust_analyzer.py17 crate, vals = cfg.split("=", 1)
18 crates_cfgs[crate] = vals.split()
39 crate = {
56 crate["proc_macro_dylib_path"] = f"{objtree}/rust/{proc_macro_dylib_name}"
58 crates.append(crate)
H A DMakefile.compiler84 --crate-type=rlib --out-dir=$(TMPOUT) --emit=obj=- - >/dev/null,$(3),$(4))
H A DMakefile.build332 --crate-type rlib -L $(objtree)/rust/ \
333 --crate-name $(basename $(notdir $@)) \
H A DKconfig.include80 rustc-option = $(success,trap "rm -rf .tmp_$$" EXIT; mkdir .tmp_$$; $(RUSTC) $(1) --crate-type=rlib…
/linux/rust/
H A DMakefile46 libmacros_name := $(shell MAKEFLAGS= $(RUSTC) --print file-names --crate-name macros --crate-type p…
49 …_name := $(shell MAKEFLAGS= $(RUSTC) --print file-names --crate-name pin_init_internal --crate-typ…
138 --crate-name $(subst rustdoc-,,$@) \
189 rustdoc-macros: private rustc_target_flags = --crate-type proc-macro \
215 --extern proc_macro --crate-type proc-macro
/linux/rust/quote/
H A DREADME.md3 These source files come from the Rust `quote` crate, version 1.0.40
/linux/rust/syn/
H A DREADME.md3 These source files come from the Rust `syn` crate, version 2.0.106
/linux/rust/proc-macro2/
H A DREADME.md3 These source files come from the Rust `proc-macro2` crate, version
/linux/Documentation/translations/zh_CN/rust/
H A Dtesting.rst42 Kernel hacking -> Rust hacking -> Doctests for the `kernel` crate
197 目前，它们主要用于测试 ``macros`` crate 的示例。
/linux/rust/pin-init/
H A DREADME.md11 > This crate was originally named [`pinned-init`], but the migration to
13 > version of the `pinned-init` crate & the `main` branch already incorporates
51 However, using the crate on stable compilers is possible by disabling `alloc`. In practice this
233 the `kernel` crate. The [`sync`] module is a good starting point.
/linux/Documentation/rust/
H A Dgeneral-information.rst99 | | +------+ +------+ | | crate | |
100 | | kernel crate | +----------+ |
H A Dcoding-guidelines.rst51 use crate::{
62 use crate::{
85 use crate::{
99 use crate::{
H A Dtesting.rst39 Kernel hacking -> Rust hacking -> Doctests for the `kernel` crate
214 Currently, they are mostly used for testing the ``macros`` crate's examples.
H A Dquick-start.rst241 ``bindgen`` uses the ``clang-sys`` crate to find a suitable ``libclang`` (which
/linux/drivers/media/dvb-frontends/
H A Dsi21xx.c637 enum fe_code_rate crate) in si21xx_setacquire() argument
654 coderate_ptr = coderates[crate]; in si21xx_setacquire()
/linux/Documentation/kbuild/
H A Dmakefiles.rst817 Kbuild will compile ``target`` using ``target.rs`` as the crate root,
818 located in the same directory as the ``Makefile``. The crate may
/linux/lib/
H A DKconfig.debug3437 bool "Doctests for the `kernel` crate" if !KUNIT_ALL_TESTS
3441 This builds the documentation tests of the `kernel` crate