diff options
| author | David S. Miller <davem@davemloft.net> | 2013-04-15 16:10:53 -0400 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2013-04-15 16:10:53 -0400 |
| commit | 61f47132dcba1eacf8fd8e64488d0b6d4bcbe4a0 (patch) | |
| tree | 97014ff57652d41b366fb41a08c93e7aa3a798e8 /drivers/net/can | |
| parent | 0022d2dd4d76e0e7d5c241c343a5016fdfa2ad4f (diff) | |
| parent | 72b270323dee45ccf4aafff7118dcc46caaed22e (diff) | |
| download | linux-3.10-61f47132dcba1eacf8fd8e64488d0b6d4bcbe4a0.tar.gz linux-3.10-61f47132dcba1eacf8fd8e64488d0b6d4bcbe4a0.tar.bz2 linux-3.10-61f47132dcba1eacf8fd8e64488d0b6d4bcbe4a0.zip | |
Merge branch 'sync_multiple'
Vlad Yasevich says:
====================
Current dev_[uc|mc]_addr_sync() API currently correctly syncs the
addresses to the first device. Any subsequent calls to sync will
not do anything since the synched variable will be set. This
variable is used as an optimization to skip over addresses that have
been synched.
There are some devices (ex: team) that attempt to do the above. There
is other work in progress that needs to above to work corretly.
The short series introduces dev_[uc|mc]_addr_synch_multiple() that
allows multiple calls to sync to multiple different devices. Original
API is left alone and still has the limitation.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/can')
0 files changed, 0 insertions, 0 deletions