similar to: [PATCH -next] drm/nouveau: uapi: fix kerneldoc warnings

Displaying 20 results from an estimated 500 matches similar to: "[PATCH -next] drm/nouveau: uapi: fix kerneldoc warnings"

2023 Jan 27
1
[PATCH drm-next 05/14] drm/nouveau: new VM_BIND uapi interfaces
On 1/27/23 02:05, Matthew Brost wrote: > On Wed, Jan 18, 2023 at 07:12:47AM +0100, Danilo Krummrich wrote: >> This commit provides the interfaces for the new UAPI motivated by the >> Vulkan API. It allows user mode drivers (UMDs) to: >> >> 1) Initialize a GPU virtual address (VA) space via the new >> DRM_IOCTL_NOUVEAU_VM_INIT ioctl. UMDs can provide a kernel
2023 Jul 25
1
[PATCH drm-misc-next v8 03/12] drm/nouveau: new VM_BIND uapi interfaces
On 7/22/23 00:58, Faith Ekstrand wrote: > > On Wed, Jul 19, 2023 at 7:15?PM Danilo Krummrich <dakr at redhat.com > <mailto:dakr at redhat.com>> wrote: > > This commit provides the interfaces for the new UAPI motivated by the > Vulkan API. It allows user mode drivers (UMDs) to: > > 1) Initialize a GPU virtual address (VA) space via the new >
2023 Jan 27
1
[PATCH drm-next 05/14] drm/nouveau: new VM_BIND uapi interfaces
Am 27.01.23 um 02:26 schrieb Danilo Krummrich: > On 1/27/23 02:05, Matthew Brost wrote: >> On Wed, Jan 18, 2023 at 07:12:47AM +0100, Danilo Krummrich wrote: >>> This commit provides the interfaces for the new UAPI motivated by the >>> Vulkan API. It allows user mode drivers (UMDs) to: >>> >>> 1) Initialize a GPU virtual address (VA) space via the new
2023 Dec 25
1
[PATCH -next] drm/nouveau: uapi: fix kerneldoc warnings
On 12/25/23 00:30, Vegard Nossum wrote: > > On 25/12/2023 08:40, Randy Dunlap wrote: >> I do see one thing that I don't like in the generated html output. >> It's not a problem with this patch. >> The #defines for DRM_NOUVEAU_VM_BIND_OP_MAP etc. have a ';' at the >> end of each line: >> >> struct drm_nouveau_vm_bind_op { >> ????
2023 Dec 25
2
[PATCH -next] drm/nouveau: uapi: fix kerneldoc warnings
On 12/24/23 22:51, Vegard Nossum wrote: > As of commit b77fdd6a48e6 ("scripts/kernel-doc: restore warning for > Excess struct/union"), we see the following warnings when running 'make > htmldocs': > > ./include/uapi/drm/nouveau_drm.h:292: warning: Excess struct member 'DRM_NOUVEAU_VM_BIND_OP_MAP' description in 'drm_nouveau_vm_bind_op' >
2023 Jan 27
0
[PATCH drm-next 05/14] drm/nouveau: new VM_BIND uapi interfaces
On 1/27/23 04:21, Matthew Brost wrote: > On Fri, Jan 27, 2023 at 02:43:30AM +0100, Danilo Krummrich wrote: >> >> >> On 1/27/23 02:05, Matthew Brost wrote: >>> On Wed, Jan 18, 2023 at 07:12:47AM +0100, Danilo Krummrich wrote: >>>> This commit provides the interfaces for the new UAPI motivated by the >>>> Vulkan API. It allows user mode drivers
2009 Feb 28
1
kernel memory access tracer
Hi On Fri, 27 Feb 2009 22:39:06 +0100 Vegard Nossum <vegard.nossum at gmail.com> wrote: > I actually wanted to ask some questions about Nouveau and the NVIDIA > drivers. I was wondering if there would be any point in extending > kmemcheck to track this driver's use of kernel memory. We could quite > easily make a "memory access tracer", which would show all the
2015 May 04
2
[Bug 11253] New: --exclude=dir doesn't work with --files-from=
https://bugzilla.samba.org/show_bug.cgi?id=11253 Bug ID: 11253 Summary: --exclude=dir doesn't work with --files-from= Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org
2014 Dec 01
3
Problem with /dev/tty in LXC established with virt-install
I have created a LXC container with debootstrap followed by virt-install like this: host=mylxc1 debootstrap wheezy /home/lxc/$host virt-install -c lxc:// -n $host --filesystem /home/lxc/$host,/ --ram 1024 I am confused about the /dev filesystem in this container. Specifically the device '/dev/tty'. >From inside the container: ~# ls -la /dev/tty ls: cannot access /dev/tty: No such
2005 Jan 13
2
coxph() and intervening events
Hello! I am using the coxph() function for counting process data. I want to include an intervening event as one of my covariates. In order to do this I have split the relevant observations in my data at the time of intervention. But I have not found any way to "inform" coxph() of the id of these observations. The result of this is that coxph() interprets the split data as
2006 Sep 18
2
Default subscriptions
Is it possible to force a subscription to an IMAP folder? So that a user by default is subscribed to folder <foo> and cannot unsubscribe. -- Vegard Svanberg <vegard at svanberg.no> [*Takapa at IRC (EFnet)]
2005 Mar 18
1
RE: problem with Dates
It seems that you have load the "survival" package date.mdy is a function from this one. In this function the "origin" of the time is the first day of 1970 in the base package the origin is the first day of 1960 it's very curious... Benjamin Esterni France From: "Vegard Andersen" <vegard.andersen@ism.uit.no> Subject: [R] Date conversion problem using
2009 Mar 04
1
file system, kernel or hardware raid failure?
I had a busy mailserver fail on me the other day. Below is what was printed in dmesg. We first suspected a hardware failure (raid controller or something else), so we moved the drives to another (identical hardware) machine and ran fsck. Fsck complained ("short read while reading inode") and asked if I wanted to ignore and rewrite (which I did). After booting up again, the problem came
2009 Feb 10
2
"failed to map segment from shared object: Cannot allocate memory"
>From /var/log/auth.log (Dovecot 1.1.4 on Ubuntu 8.10): Feb 10 08:29:06 home dovecot-auth: PAM unable to dlopen(/lib/security/pam_ck_connector.so): libdbus-1.so.3: failed to map segment from shared object: Cannot allocate memory Feb 10 08:29:06 home dovecot-auth: PAM adding faulty module: /lib/security/pam_ck_connector.so English, please? :) Strangely, it seemed to disappear after increasing
2004 Jun 02
2
dovecot and virtual hosting
Hi. A usual hosting provider setup depends on having one IP ("virtual mailserver") per domain. Using dovecot on servers handling hundreds or thousands of domains today equals to having multiple instances of dovecot running. This problem could be solved by making dovecot take into account the IP address the user connects to and authenticate against the proper {database, table,
2011 Jul 18
3
Performance with 200k messages in Maildir
What should I expect performance-wise if I put 200000 messages in a Maildir store and use two or three MUAs (mutt and Thunderbird), on an Athlon dual core 2GHz with SATA drives in software RAID (Linux)? Like; would it be useless/crawling, usable or pretty fast. I imagine MUA startup / first time folder read would be slow, but daily use more or less ok. Thanks to Dovecot's indexing, I imagine
2009 Mar 04
2
deliver to root
Hi, we use dovecot 1.1.11 on a RH Server with sendmail. Local delivery is done with deliver: Mlocal, P=/usr/local/libexec/dovecot/deliver, F=lsDFMAw5:/|@qSPfhn9, S=EnvFromL/HdrFromL, R=EnvToL/HdrToL, T=DNS/RFC822/X-Unix, A=deliver -d $u This setup works without issues for us, but mail to root has a problem with deliver: deliver(root): Mar 04 16:31:31
2005 Jan 09
1
dovecot adds "Status: O"
Dovecot adds the "Status: O" header when users download their email. Why? -- Vegard Svanberg <vegard at svanberg.no> [*Takapa at IRC (EFnet)]
2008 May 28
1
"storage error during logout"
What is this error message actually trying to tell me? May 28 13:47:24 yyy dovecot: POP3(aaa at bbb): Disconnected: Storage error during logout. top=0/0, retr=2/73195, del=0/435, size=13509375 This user is accessing his mailbox using both POP3 and IMAP, I don't know if that's relevant. The POP3 check is quite aggressive; once every minute or so. Dovecot 1.0.13-1~bpo40+1 -- Vegard
2011 Jun 16
1
Vacation -- reply to another address than envelope from
Vacation (Sieve) replies to the envelope address. However, I have a customer which receive e-mails from a service which sends e-mails on behalf of a user (submitted through a web form). So an e-mail would be like (envelope from and from-header is webformfromwhatever at foobar.com): From: webformfromwhatever at foobar.com To: mycustomer at hisdomain.com Reply-To: usersrealmailaddress at