| /freebsd/usr.bin/posixmqcontrol/ |
| H A D | posixmqcontroltest8x64.sh | 5 topic='/test123'
7 ${subject} info -q "$topic" 2>/dev/null
9 echo "sorry, $topic exists."
14 ${subject} create -q "$topic" -s 64 -d 8
19 info=$(${subject} info -q "$topic")
48 ${subject} send -q "$topic" -c "message $i" -p "$i"
54 info=$(${subject} info -q "$topic")
70 actual=$(${subject} recv -q "$topic")
81 info=$(${subject} info -q "$topic")
93 ${subject} rm -q "$topic"
|
| H A D | posixmqcontroltest8qs.sh | 10 topic="${prefix}${i}"
11 ${subject} info -q "${topic}" 2>/dev/null
13 echo "sorry, $topic exists."
16 list="${list} -q ${topic}"
37 topic="${prefix}${i}"
38 ignore=$( ${subject} recv -q "${topic}" )
|
| /freebsd/stand/common/ |
| H A D | commands.c | 53 * Subtopic entries must immediately follow the topic (this is used to
61 help_getnext(int fd, char **topic, char **subtopic, char **desc) in help_getnext() argument
66 *topic = *subtopic = *desc = NULL; in help_getnext()
77 if (*cp == 'T' && *topic == NULL) { in help_getnext()
80 *topic = strdup(cp + 1); in help_getnext()
91 if (*topic == NULL) { in help_getnext()
102 help_emitsummary(char *topic, char *subtopic, char *desc) in help_emitsummary() argument
107 pager_output(topic); in help_emitsummary()
108 i = strlen(topic); in help_emitsummary()
128 char *topic, *subtopic, *t, *s, *d; in command_help() local
[all …]
|
| /freebsd/contrib/kyua/cli/ |
| H A D | cmd_about.cpp | 145 const std::string& topic = cmdline.arguments()[0]; in run() local
147 if (topic == "authors") { in run()
150 } else if (topic == "license") { in run()
152 } else if (topic == "version") { in run()
155 throw cmdline::usage_error(F("Invalid about topic '%s'") % topic); in run()
|
| /freebsd/sys/dev/pccbb/ |
| H A D | pccbbreg.h | 133 /* ToPIC 95 ONLY */
136 /* ToPIC 97, 100 */
140 /* TOPIC 95+ */
151 /* TOPIC 95+ */
156 /* The following bits may be for ToPIC 95 only */
166 /* TOPIC 95+ */
|
| /freebsd/lib/libpmc/pmu-events/ |
| H A D | README | 26 such as Pipelining, Cache, Memory, Floating-point etc. All events for a topic
28 the topic. Eg: "Floating-point.json".
30 All the topic JSON files for a CPU model/family should be in a separate
|
| H A D | jevents.c | 291 static char *topic; variable
299 i = asprintf(&tp, "%s", topic); in get_topic()
321 free(topic); in add_topic()
322 topic = strdup(bname); in add_topic()
323 if (!topic) { in add_topic()
333 char *topic; member
348 char *topic_local = pd->topic; in print_events_table_entry()
363 fprintf(outfp, "\t.topic = \"%s\",\n", topic_local); in print_events_table_entry()
1118 /* model directory, reset topic */ in process_one_file()
1203 .topic in process_one_file()
[all...] |
| H A D | pmu-events.h | 20 const char *topic; member
|
| /freebsd/sys/contrib/openzfs/contrib/pyzfs/ |
| H A D | setup.py.in | 39 "Topic :: System :: Filesystems",
40 "Topic :: Software Development :: Libraries",
|
| /freebsd/sys/contrib/device-tree/Bindings/power/supply/ |
| H A D | ltc4162-l.yaml | 2 # Copyright (C) 2020 Topic Embedded Products
11 - Mike Looijmans <mike.looijmans@topic.nl>
|
| H A D | ltc2941.txt | 21 Example from the Topic Miami Florida board:
|
| /freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/cli_root/zfs_program/ |
| H A D | zfs_program_json.ksh | 122 For further help on a command or topic, run: zfs help [<topic>]")
|
| /freebsd/sys/contrib/zstd/ |
| H A D | CONTRIBUTING.md | 31 will use a new branch per sizable topic. For smaller changes, it is okay to lump multiple
47 * Topic and development:
48 * Make a new branch on your fork about the topic you're developing for
105 …* Just because your changes have been merged does not mean the topic or larger issue is complete. …
191 would-be PR. Of course, just because a topic has already been discussed (and perhaps rejected
193 it will be helpful for you to have context from that topic's history before contributing.
387 It's a pretty long topic, which is difficult to summarize in a single paragraph.
|
| /freebsd/contrib/sendmail/src/ |
| H A D | helpfile | 20 smtp For more info use "HELP <topic>".
24 help HELP [ <topic> ]
|
| /freebsd/sys/contrib/openzfs/cmd/zed/zed.d/ |
| H A D | zed.rc | 159 # Ntfy topic
160 # This defines which topic will receive the ntfy notification.
|
| H A D | zed-functions.sh | 541 # The ntfy topic (ZED_NTFY_TOPIC) identifies the topic that the notification
545 # access token that could be used if a topic is read/write protected. If a
546 # topic can be written to publicaly, a ZED_NTFY_ACCESS_TOKEN is not required.
|
| /freebsd/contrib/llvm-project/clang/include/clang/Basic/ |
| H A D | TargetCXXABI.def | 50 /// /help/topic/com.arm.doc.ihi0041c/IHI0041C_cppabi.pdf
69 /// /help/topic/com.arm.doc.ihi0059a/IHI0059A_cppabi64.pdf
|
| /freebsd/contrib/file/python/ |
| H A D | setup.py | 26 'Topic :: Software Development :: Libraries :: Python Modules',
|
| /freebsd/sys/contrib/device-tree/Bindings/iio/adc/ |
| H A D | ti,ads1100.yaml | 10 - Mike Looijmans <mike.looijmans@topic.nl>
|
| H A D | ti,ads1298.yaml | 14 - Mike Looijmans <mike.looijmans@topic.nl>
|
| /freebsd/contrib/file/magic/Magdir/ |
| H A D | microfocus | 6 # https://documentation.microfocus.com/help/index.jsp?topic=\
|
| /freebsd/sys/contrib/device-tree/Bindings/arm/ |
| H A D | juno,scpi.txt | 26 [1] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0922b/apas03s22.html
|
| /freebsd/sys/contrib/device-tree/Bindings/iio/accel/ |
| H A D | bosch,bmi088.yaml | 10 - Mike Looijmans <mike.looijmans@topic.nl>
|
| /freebsd/contrib/libucl/python/ |
| H A D | setup.py | 69 "Topic :: Software Development :: Libraries",
|
| /freebsd/contrib/kyua/doc/ |
| H A D | kyua-about.1.in | 61 the desired topic as the single argument to the command.
|