rpmsg: rpmsg_send() operations takes rpmsg_endpoint

The rpmsg_send() operations has been taking a rpmsg_device, but this
forces users of secondary rpmsg_endpoints to use the rpmsg_sendto()
interface - by extracting source and destination from the given data
structures. If we instead pass the rpmsg_endpoint to these functions a
service can use rpmsg_sendto() to respond to messages, even on secondary
endpoints.

In addition this would allow us to support operations on multiple
channels in future backends that does not support off-channel
operations.

Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

1 files changed, 2 insertions, 2 deletions

diff --git a/samples/rpmsg/rpmsg_client_sample.c b/samples/rpmsg/rpmsg_client_sample.c

path: root/README

 inotail - inotify enhanced tail
o===============================o

inotail is a drop-in replacement for the 'tail' program found in the base
installation of every Linux/UNIX system. It makes use of the Inotify
infrastructure in recent version of the Linux kernel to speed up tailing files
in the follow mode (the '-f' option). Currently inotail is not fully compatible
to neither POSIX or GNU tail but might be in the future.

Requirements
------------
- Linux kernel 2.6.13 or higher with CONFIG_INOTIFY enabled
- Future versions will require a version of the glibc shipping with inotify
  support

License
-------
inotail is licensed under the terms of the GNU General Public License Version 2.
You can find the full text in the file LICENSE in the source tree of inotail.

-- Tobias Klauser <tklauser@distanz.ch>