search for: described

...lose_work() error: uninitialized symbol 'rc'. fs/smb/client/file.c:732 _cifsFileInfo_put() error: uninitialized symbol 'rc'. Error/Warning ids grouped by kconfigs: gcc_recent_errors |-- alpha-allnoconfig | |-- mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node | `-- mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node |-- alpha-allyesconfig | |-- drivers-gpu-drm-imx-ipuv3-imx-ldb.c:error:_sel-directive-output-may-be-truncated-writing-bytes-into-a-region-of-size-between-and | |-...

...er' not found drivers/usb/typec/class.c:1: warning: 'typec_altmode_unregister_notifier' not found drivers/usb/typec/class.c:1: warning: 'typec_altmode_register_notifier' not found include/linux/w1.h:272: warning: Function parameter or member 'of_match_table' not described in 'w1_family' include/linux/lsm_hooks.h:1811: warning: Function parameter or member 'quotactl' not described in 'security_list_options' include/linux/lsm_hooks.h:1811: warning: Function parameter or member 'quota_on' not described in 'security_list_options...

...{Hmisc} which allows for weights, but has no functionality for subdivision. I tried using a by() function with describe{Hmisc}: by(cbind(my, variables, here), division.variable, describe, weights=weight.variable) but found that this returns an error message stating that the variables to be described and the weights variable are not the same length: Error in describe.vector(xx, nam[i], exclude.missing = exclude.missing, : length of weights must equal length of x In addition: Warning message: In present & !is.na(weights) : longer object length is not a multiple of shorter object...

This is the next version of my patch series for teaching DRM how to automatically create debugfs nodes for drivers with MST topologies. This was originally intended just for nouveau, but has since been expanded to all DRM drivers. Cc: Maarten Lankhorst <maarten.lankhorst at linux.intel.com> Cc: Daniel Stone <daniel at fooishbar.org> Lyude Paul (4): drm/debugfs: Add support for

Hi, I want to be able to get at the described class in my shared behaviour. I''m sure an example will say it better than my words describe "my shared", :shared => true do it "should tell me what the class is its describing" do how_do_i_get_the_user_class_here end end describe User do it_should_behav...

I''ve been reading through the Rspec book to see if I missed any tricks, and the discussion of before block use for context setup in sec 12.6 struck me as interesting and something I had a knee-jerk reaction to. I think that when you are using nested examples to describe a context change it is bad practice to allow any example within that group to run outside of that context. This could

This series cleans up duplicated code for replacing firmware FB driver with proper DRI driver and adds handover support to Tegra driver. This is a sligtly updated version of a series sent on 24 Nov 2017. --- v2: - rebased on current drm-next - dropped staging/sm750fb changes - added kernel docs for DRM helpers v3: - move kerneldoc to fbdev, where functions are implemented - split kerneldoc

This series cleans up duplicated code for replacing firmware FB driver with proper DRI driver and adds handover support to Tegra driver. This is a sligtly updated version of a series sent on 24 Nov 2017. --- v2: - rebased on current drm-next - dropped staging/sm750fb changes - added kernel docs for DRM helpers v3: - move kerneldoc to fbdev, where functions are implemented - split kerneldoc

Is it possible to access the described class in a shared behavior? I''m trying to do something like this: describe "Siberian feline", :shared => true do described_class_instance_as :feline, :name => "fluffy", :breed => "Siberian" # or maybe before(:all) do @feline = described_c...

Hi all, There are currently a number of ways to extend RSpec that are documented inconsistently and work in sometimes conflicting and/or confusing ways. I''d like to resolve that. The recent addition of Spec::Runner.configure is part of that resolution. The thing I want to tackle now is the stuff that happens before and after each example. Currently (in trunk), things are executed in the

Hello, in the tunk, i found a new style for spec: describe Foo do it "should do bar" do ... end end instead of context "Foo" context "should do bar" ... end end The Rails-Textmate-bundle in trunk use only the new "describe-it" style, What are the reasons for the new style ? Shall i use the new style from now on ? Hussein

In 1.0.8 I am able to nest describe blocks, but in moving to trunk, revision 2971, I am unable to have the expected results. Here is an example nested describe block: describe "foo" do describe "with no arguments" do before do puts "a" end it "should" do puts "SHOULD" end end describe "with invalid

Many DRM drivers implement an encoder with an empty implementation. This patchset adds drm_simple_encoder_init() and drm_simple_encoder_create(), which can be used by drivers instead. Except for the destroy callback, the simple encoder's implementation is empty. The patchset also converts 4 encoder instances to use the simple-encoder helpers. But there are at least 11 other drivers which can

Hi all, Just wondering about this: I''ve been dealing with classes/modules nested in several layers of namespaces. Here would be an example of a describe block: describe ClassOne::ClassTwo::ClassThree, "description here" do ... end What would be the easiest way to write something a little more terse, like: describe ClassThree, "description here" do ... end

I am having an issue where a feature works fine but the corresponding test fails, and I can''t understand why. I created a mock application to demonstrate the problem. https://github.com/assafshomer/clear_button All it does is show an input form with a clear button. The clearing happens by redirecting back to the same form. It does clear it when you run the app, but the test for it

This is the next version of https://patchwork.freedesktop.org/series/46815/ With a lot more thought put into it so as to avoid the potential deadlock scenarios I missed. This also required fixing some bogus DRM helper usage. Try and deadlock me now, nouveau. I dare you!!! Lyude Paul (8): drm/nouveau: Fix bogus drm_kms_helper_poll_enable() placement drm/nouveau: Enable polling even if we

...f some of the fields we report the possible configurations for. Note that these values are reported individually and all combinations aren't necessarily supported. The last section 'features' describes whether some high-level features supported by such a VM. The features themselves are described in the documentation above. Note that the entries into 'features' are added arbitrarily depending on whether a feature is deemed important enough to be exposed. So please feel free to report if anything is missing or it would be helpful if we reported any feature. --- Now specifically to...

As first discussed in the giant "New LLVM git repository conversion prototype" thread, I've pushed a git tag that allows git-describe to be used for generating human readable commit names on master. The tag is "llvmorg-10-init", to be interpreted as "the initial commit with major version number 10". The idea is to add similar tags along with future version bumps.

I am trying to use Rails and an Oracle 7 database. I have the following error message: (eval):3:in `__send__'': ORA-12663: Services required by client not available on the server (OCIError) from (eval):3:in `describe'' and the line oracle_adapter,rb:361: (owner, table_name) = @connection.describe(table_name) Do I need this describe line? Can I replace with something else just

Hi All, I'm trying to automate a data summary using summary or describe from the HMisc package. I want to stratify my data set by patient_type. I was hoping to do something like: Describe(myDataFrame ~ patient_type) I can create data subsets and run the describe function one at a time, but there's got to be a better way. Any suggestions? Rachel [[alternative HTML