search for: next_id

I have this in a model: has_one :next, :class_name=>''WorkPart'', :foreign_key=>''next_id'' And it causes this error: compile error /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_record/deprecated_associations.rb:83: void value expression /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.13.1/lib/active_record/deprecated_associations.rb:84:in `deprecated_ha...

...attr_group; Shouldn't this be a pointer to a list of groups? > + struct device *sdev; Shouldn't this be embedded inside here, instead of a pointer? > + struct mic_mw aper; > +}; > +/** > + * struct mic_info - Global information about all MIC devices. > + * > + * @next_id: Next available MIC device id. > + * @mic_class: Class of MIC devices for sysfs accessibility. > + * @mdev_id: Base device node number. > + */ > +struct mic_info { > + int next_id; Please use the idr interface, don't roll your own, odds are you got it wrong, and I don't want...

...attr_group; Shouldn't this be a pointer to a list of groups? > + struct device *sdev; Shouldn't this be embedded inside here, instead of a pointer? > + struct mic_mw aper; > +}; > +/** > + * struct mic_info - Global information about all MIC devices. > + * > + * @next_id: Next available MIC device id. > + * @mic_class: Class of MIC devices for sysfs accessibility. > + * @mdev_id: Base device node number. > + */ > +struct mic_info { > + int next_id; Please use the idr interface, don't roll your own, odds are you got it wrong, and I don't want...

...er need to be reogranized. I think it would be preferrable to use a sequence, but haven''t found a way of doing this with MySQL, so I just increment the max value of the id column. Here''s how I generate a customer number: application.rb: CUSTOMER_BASE = "10000" def next_id(table_name, column) ActiveRecord::Base.connection.select_value("select max(#{column})+1 from #{table_name}") end customer_controller.rb: def create @customer.number = CUSTOMER_BASE.to_i + next_id(''customers'', ''id'').to_i end Have I simply po...

...225c)}, + {PCI_DEVICE(PCI_VENDOR_ID_INTEL, MIC_X100_PCI_DEVICE_225d)}, + {PCI_DEVICE(PCI_VENDOR_ID_INTEL, MIC_X100_PCI_DEVICE_225e)}, + + /* required last entry */ + { 0, } +}; + +MODULE_DEVICE_TABLE(pci, mic_pci_tbl); + +/** + * struct mic_info - Global information about all MIC devices. + * + * @next_id: Next available MIC device id. + * @mic_class: Class of MIC devices for sysfs accessibility. + * @mdev_id: Base device node number. + */ +struct mic_info { + int next_id; + struct class *mic_class; + dev_t mdev_id; +}; + +/* g_mic - Global information about all MIC devices. */ +static struct mic_in...

...225c)}, + {PCI_DEVICE(PCI_VENDOR_ID_INTEL, MIC_X100_PCI_DEVICE_225d)}, + {PCI_DEVICE(PCI_VENDOR_ID_INTEL, MIC_X100_PCI_DEVICE_225e)}, + + /* required last entry */ + { 0, } +}; + +MODULE_DEVICE_TABLE(pci, mic_pci_tbl); + +/** + * struct mic_info - Global information about all MIC devices. + * + * @next_id: Next available MIC device id. + * @mic_class: Class of MIC devices for sysfs accessibility. + * @dev: Range for device node numbers. + */ +struct mic_info { + int next_id; + struct class *mic_class; + dev_t dev; +}; + +/* g_mic - Global information about all MIC devices. */ +static struct mic_info...

ChangeLog: ========= v1 => v2: a) License wording cleanup, sysfs ABI documentation, patch 1 refactoring into 3 smaller patches and function renames, as per feedback from Greg Kroah-Hartman. b) Use VRINGH infrastructure for accessing virtio rings from the host in patch 5, as per feedback from Michael S. Tsirkin. v1: Initial post @ https://lkml.org/lkml/2013/7/24/810 Description:

ChangeLog: ========= v1 => v2: a) License wording cleanup, sysfs ABI documentation, patch 1 refactoring into 3 smaller patches and function renames, as per feedback from Greg Kroah-Hartman. b) Use VRINGH infrastructure for accessing virtio rings from the host in patch 5, as per feedback from Michael S. Tsirkin. v1: Initial post @ https://lkml.org/lkml/2013/7/24/810 Description:

An Intel MIC X100 device is a PCIe form factor add-in coprocessor card based on the Intel Many Integrated Core (MIC) architecture that runs a Linux OS. It is a PCIe endpoint in a platform and therefore implements the three required standard address spaces i.e. configuration, memory and I/O. The host OS loads a device driver as is typical for PCIe devices. The card itself runs a bootstrap after

An Intel MIC X100 device is a PCIe form factor add-in coprocessor card based on the Intel Many Integrated Core (MIC) architecture that runs a Linux OS. It is a PCIe endpoint in a platform and therefore implements the three required standard address spaces i.e. configuration, memory and I/O. The host OS loads a device driver as is typical for PCIe devices. The card itself runs a bootstrap after