On Mon, 2009-07-27 at 18:29 -0700, Luis R. Rodriguez wrote: > Signed-off-by: Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> > --- > > Did this in a flash, so just want to see if this is you like this > approach. Of course a lot of cleaning can be done here but ignore that > for now (like the fact that beacon hint doesn't really process IEs, > and the functions names used here). > > This just compiles for me, never tested it. Looks ok, but I don't see why you need this type enum? > + * enum beacon_hint_type - type of regulatory beacon hint I mean -- if the beacon was received we could just process it as before, and if it also has a country IE we can just process that additionally? Why bother doing both separately? Also, I would have allocated the struct and the space for the IE together, but that really doesn't matter :) johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
