search for: mandatorily

Hi, not sure if this is the best place to ask this statistical question, but here it goes: Does doing survival analysis mandatorily require consecutively recruited patients? If I have a retrospective patient sample, but not consecutively recruited, does it necessitate invalidity of the use of survival analysis (for example: Kaplan Meier analysis or Cox regression, etc). Or as long as the patient sample is a random sample of the...

...ds ) Then I do a clustering with Ward method and euclidean distance, using the cvmatrix and I get a dendrogram. This part is not the problem, so I'll go directly to what I want. I would like to calculate the mean correlation between the elements of each cluster. Since clustering methods will mandatorily produce clusters, I'd like to know if the elements of my clusters are correlated (I mean, if the clusters are valid). I believe this might not be very complicated, given that I have all the elements. I just don't know how to do it on R. I tried to do the clustering with p-values for each...

...rom * @file_priv: drm file-private structure * @handle: buffer handle to export - * @flags: flags like DRM_CLOEXEC + * @flags: flags like DRM_CLOEXEC or DRM_SYNC_FD * @prime_fd: pointer to storage for the fd id of the create dma-buf * * This is the PRIME export function which must be used mandatorily by GEM @@ -401,6 +403,24 @@ int drm_gem_prime_handle_to_fd(struct drm_device *dev, struct drm_gem_object *obj; int ret = 0; struct dma_buf *dmabuf; + struct fence *fence = NULL; + + if (flags & DRM_SYNC_FD) { +#ifdef CONFIG_SYNC + struct sync_fence *sf = sync_fence_fdget(*prime_fd); + i...

Hello, I am writing a script which reads and writes vorbis comments using the vorbiscomment utility from vorbis-tools. I have just one question regarding the --raw switch. Raw mode (--raw, -R) will read and write comments in utf8, rather than converting to the user's character set. This is useful for using vorbiscomment in scripts. However, this is not sufficient for general

Hello, I am writing a script which reads and writes vorbis comments using the vorbiscomment utility from vorbis-tools. I have just one question regarding the --raw switch. Raw mode (--raw, -R) will read and write comments in utf8, rather than converting to the user's character set. This is useful for using vorbiscomment in scripts. However, this is not sufficient for general

...rivate structure > * @handle: buffer handle to export > - * @flags: flags like DRM_CLOEXEC > + * @flags: flags like DRM_CLOEXEC or DRM_SYNC_FD > * @prime_fd: pointer to storage for the fd id of the create dma-buf > * > * This is the PRIME export function which must be used mandatorily by GEM > @@ -401,6 +403,24 @@ int drm_gem_prime_handle_to_fd(struct drm_device *dev, > struct drm_gem_object *obj; > int ret = 0; > struct dma_buf *dmabuf; > + struct fence *fence = NULL; > + > + if (flags & DRM_SYNC_FD) { > +#ifdef CONFIG_SYNC > + struct sync_...

Dear Team, The OpenLDAP stuff on this page: http://us4.samba.org/samba/docs/man/Samba-Guide/happy.html is not the preferred backend, i.e. ldbm, it really, really needs to be bdb. See: http://www.openldap.org/faq/index.cgi?_highlightWords=bdb%20ldbm&file=1085 "ldbm uses a neutral storage interface which in principle could wrap dbm, ndbm, gdbm or sleepycat as underlying storage;

...if (IS_ERR(dmabuf)) { > /* normally the created dma-buf takes ownership of the ref, > * but if that fails then drop the ref > @@ -419,7 +415,7 @@ static struct dma_buf *export_and_register_object(struct drm_device *dev, > * This is the PRIME export function which must be used mandatorily by GEM > * drivers to ensure correct lifetime management of the underlying GEM object. > * The actual exporting from GEM object to a dma-buf is done through the > - * &drm_driver.gem_prime_export driver callback. > + * &drm_gem_object_funcs.export callback. > */ > i...

...export(obj, flags); if (IS_ERR(dmabuf)) { /* normally the created dma-buf takes ownership of the ref, * but if that fails then drop the ref @@ -419,7 +415,7 @@ static struct dma_buf *export_and_register_object(struct drm_device *dev, * This is the PRIME export function which must be used mandatorily by GEM * drivers to ensure correct lifetime management of the underlying GEM object. * The actual exporting from GEM object to a dma-buf is done through the - * &drm_driver.gem_prime_export driver callback. + * &drm_gem_object_funcs.export callback. */ int drm_gem_prime_handle_to_fd(...

...export(obj, flags); if (IS_ERR(dmabuf)) { /* normally the created dma-buf takes ownership of the ref, * but if that fails then drop the ref @@ -419,7 +415,7 @@ static struct dma_buf *export_and_register_object(struct drm_device *dev, * This is the PRIME export function which must be used mandatorily by GEM * drivers to ensure correct lifetime management of the underlying GEM object. * The actual exporting from GEM object to a dma-buf is done through the - * &drm_driver.gem_prime_export driver callback. + * &drm_gem_object_funcs.export callback. */ int drm_gem_prime_handle_to_fd(...

Hi guys, I'd like to start a new thread about explicit fence synchronization. This time with a Nouveau twist. :-) First, let me define what I understand by implicit/explicit sync: Implicit synchronization * Fences are attached to buffers * Kernel manages fences automatically based on buffer read/write access Explicit synchronization * Fences are passed around independently * Kernel takes

The GEM and PRIME related callbacks in struct drm_driver are deprecated in favor of GEM object functions in struct drm_gem_object_funcs. This patchset converts the remaining drivers to object functions and removes most of the obsolete interfaces. Patches #1 to #18 convert DRM drivers to GEM object functions, one by one. Each patch moves existing callbacks from struct drm_driver to an instance of

The GEM and PRIME related callbacks in struct drm_driver are deprecated in favor of GEM object functions in struct drm_gem_object_funcs. This patchset converts the remaining drivers to object functions and removes most of the obsolete interfaces. Patches #1 to #16 and #18 to #19 convert DRM drivers to GEM object functions, one by one. Each patch moves existing callbacks from struct drm_driver to

The GEM and PRIME related callbacks in struct drm_driver are deprecated in favor of GEM object functions in struct drm_gem_object_funcs. This patchset converts the remaining drivers to object functions and removes most of the obsolete interfaces. Version 3 of this patchset mostly fixes drm_gem_prime_handle_to_fd and updates i.MX's dcss driver. The driver was missing from earlier versions and