search for: st_id

...; longititudes. The KS file contains all the data I need to maniuplate. But > I need to connect the latitude and longitude given in the US file to the > KS file. They are connected by station number. > I am trying to use a which function to sort through the two data sets > finding where ST_ID (USA file) is equal to the ID ( KS file) and finding > the latitudes where this is true. > >> xlat <- lat[which(ST_ID == ID, arr.ind == FALSE)] > Error in which(ST_ID == ID, arr.ind == FALSE) : > object 'arr.ind' not found > In addition: Warning message: > In...

This is a forward port for net_proc.c from 1.2.

The only non-fix here is Joel's new configfs convenience macros, but nobody is using them yet, so I think the patch is safe. By the way, these patches (as usual) are all rebased on top of your latest tree. I think that since the vast majority of ocfs2 and configfs patches are self-contained and within a small area of the kernel that this should probably be fine. If you feel otherwise however,

...oid o2net_set_nst_sock_container(struct o2net_send_tracking *nst, struct o2net_sock_container *sc) { nst->st_sc = sc; } -void o2net_set_nst_msg_id(struct o2net_send_tracking *nst, u32 msg_id) +static void o2net_set_nst_msg_id(struct o2net_send_tracking *nst, u32 msg_id) { nst->st_id = msg_id; } + +#else /* CONFIG_DEBUG_FS */ + +static inline void o2net_init_nst(struct o2net_send_tracking *nst, u32 msgtype, + u32 msgkey, struct task_struct *task, u8 node) +{ +} + +static inline void o2net_set_nst_sock_time(struct o2net_send_tracking *nst) +{ +} + +static inline void o2ne...

I'm running a bit late with the e-mail this time around, but I think that's ok since there really isn't any major new features here - the bulk of the Ocfs2 update is bug fixes, or cleanups. The same goes for configfs. The only two things that could be described as features would be: - Sunil has updated Ocfs2 to provide even more live cluster locking information via debugfs. - Joel