search for: consolidating

...variable names, this consolidation effort has resulted in some cleanup with regards to structure and variable names: a) Some of the badly named structures have been eliminated (struct driver_context etc.) while hopefully all newly introduced names are acceptable. Patches 1 through 11 deal with consolidating the device driver state while patches 12 through 16 deal with consolidating device state. Regards, K. Y

...variable names, this consolidation effort has resulted in some cleanup with regards to structure and variable names: a) Some of the badly named structures have been eliminated (struct driver_context etc.) while hopefully all newly introduced names are acceptable. Patches 1 through 11 deal with consolidating the device driver state while patches 12 through 16 deal with consolidating device state. Regards, K. Y

Dear List, I'm getting the error: object of type 'closure' is not subsettable And am not sure how to get around the problem. I've included two short code sets below. One that shows what I want to do and works, but without using the function much, and another that tries to use the function but causes the error. # THIS WORKS AND SHOWS WHAT I'D LIKE TO DO a <- c(1,2,3) b

Hello Everyone, I have recently been introduced to the ggplot package by Hadley Wickham and must say I am quite impressed so far at how easy it is to make attractive plots, but one thing I am struggling over is how to consolidate legends. I have 3 plots that I would like to put on a single page and all 3 map the same dimension of the data to the colour aesthetic. Right now, when I plot all

Hi Bert, Thank you, yes, you are right. I want to consolidate the three functions into one functions by adding more arguments, adding flexibility to accommodate the number of clusters or the number of Kaplan Meier curves generated in one figure. So, I just need to define one function. Thanks, Ding From: Bert Gunter [mailto:bgunter.4567 at gmail.com] Sent: Sunday, January 14, 2018 9:50 AM

On Thu, Mar 1, 2018 at 5:13 PM, Bjorn Helgaas <helgaas at kernel.org> wrote: > On Thu, Mar 01, 2018 at 06:40:47AM +0100, Jan Kiszka wrote: >> From: Jan Kiszka <jan.kiszka at siemens.com> >> >> Since e279b6c1d329 ("x86: start unification of arch/x86/Kconfig.*"), we >> have two PCI_MMCONFIG entries, one from the original i386 and another >> from

Hello, the same parameter for colour and shape aesthetics gives 2 legends: library(ggplot2) p <- ggplot(mtcars, aes(x=wt, y=mpg)) p + geom_point(aes(colour=factor(cyl), shape=factor(cyl))) Can the 2 legends be consolidated to one with colours and shapes of the symbols matched between legend and plot ? Thank you Bernd Engelmann bernd.engelmann at amd.com phone: + 49-351-277-4545 fax: +

...a separate digest list; subscribers to linux-alert-digest tended to receive the same number of e-mail messages as subscribers to linux-alert, only with an additional time lag of up to a week--pretty silly considering that linux-alert information can often be rather time critical! We had considered consolidating these lists on several occasions in the past. The recent move of the security lists from NRAO to Red Hat seemed like an opportune time to do this and so we finally went ahead and did it. Basically, what we (Marc Ewing, actually) have done is removed the linux-alert-digest list and merged its subs...

Howdy, I am trying to migrate several scripts to use application defined types, and am running into a few issues. When I attempt to run a script with a application defined type, it looks like the DTrace preprocessor is getting angry with me: $ cat view.d #include "httpd.h" :::acceptconnection { this->addr = (conn_rec *)copyin(arg0,sizeof(conn_rec *)); } $ dtrace -C

...ache_t wdcache = {0, 0, 0}; @wdcache = dso_local global %struct.dstack zeroinitializer, align 8, !dbg !1189 If I directly compile the .c file to .ll, I will not see this problem. Is there a way to still use the configure/make toolchain, yet still maintain the original type information instead of consolidating types of the same data? Thanks. -- Regards, Peng

From: Jan Kiszka <jan.kiszka at siemens.com> Since e279b6c1d329 ("x86: start unification of arch/x86/Kconfig.*"), we have two PCI_MMCONFIG entries, one from the original i386 and another from x86_64. This consolidates both entries into a single one. The logic for x86_32, where this option was not under user control, remains identical. On x86_64, PCI_MMCONFIG becomes additionally

From: Jan Kiszka <jan.kiszka at siemens.com> Since e279b6c1d329 ("x86: start unification of arch/x86/Kconfig.*"), we have two PCI_MMCONFIG entries, one from the original i386 and another from x86_64. This consolidates both entries into a single one. Signed-off-by: Jan Kiszka <jan.kiszka at siemens.com> --- arch/x86/Kconfig | 11 ++++------- 1 file changed, 4 insertions(+),

Hi Am 17.03.23 um 13:39 schrieb Javier Martinez Canillas: > Thomas Zimmermann <tzimmermann at suse.de> writes: > >> Consolidate all handling of CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM by >> making the module parameter optional in drm_fb_helper.c. >> >> Without the config option, modules can set smem_start in struct >> fb_info for internal usage, but not export

How do I generate a consolidated set of rdocs for my local rails installation like the docs at api.rubyonrails.com? Currently I have the rdocs for each package ( actionpack, activerecord, etc... ) that were autogenerated when I downloaded the gems. Is the api.rubyonrails site doing something special or is there a rake task that will generate my local docs the same way? Thanks! -- Posted

Hi everyone! Thank you for the help you have been given to me, and here I'm with another problem with my dataframes: I have two dataframes (with much more observations), like these: Dataframe1 Firm Year cash 500400200 2007 100 500400200 2006 200 500400200 2005 400 500400300 2007 300 500400300 2006 240 500400300 2005 120 500400400

We felt that it would be good to let you know about some minor changes happening with our community services. For quite some time, we've had a consolidated authentication server for most of our community services. This means that you use the same username and password for issues.asterisk.org, wiki.asterisk.org and code.asterisk.org. ReviewBoard (reviewboard.asterisk.org) still uses its own

We felt that it would be good to let you know about some minor changes happening with our community services. For quite some time, we've had a consolidated authentication server for most of our community services. This means that you use the same username and password for issues.asterisk.org, wiki.asterisk.org and code.asterisk.org. ReviewBoard (reviewboard.asterisk.org) still uses its own

What LoopVectorize.cpp has are the following. Each function may have to have a separate consolidation discussion. I'm bringing up getpointerOperand() since I actually found multiple instances defined/used. DependenceAnalysis.cpp has isLoadOrStore(). LoopAccessAnalysis.cpp has getAddressSpaceOperand(). I'm sure there are others that might be worth discussing within this thread or a follow

On 30 August 2016 at 00:01, Sean Paul <seanpaul at google.com> wrote: > On Mon, Aug 29, 2016 at 9:02 AM, Baoyou Xie <baoyou.xie at linaro.org> wrote: > > We get 1 warning when build kernel with W=1: > > drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgm107.c:937:1: warning: no > previous prototype for 'gm107_grctx_generate_tpcid' [-Wmissing-prototypes] > >

...ns here? Should we plan to do that consolitdation based on > your new version, or just add clock_gettime64 in arm32 and x86-32, and then > be done with it? The other ones will obviously still be fast for 32-bit time_t > and will have a working non-vdso sys_clock_getttime64(). In principle consolidating all those implementations should be possible to some extent and probably worthwhile. What's arch specific are the actual accessors to the hardware clocks. > I also wonder about clock_getres(): half the architectures seem to implement > it in vdso, but notably arm32 and x86 don't, and...