> > > Device driver should log via DPDK log, not to printf which is
> > > sends to /dev/null in a daemon application.
> > >
> > > Signed-off-by: Stephen Hemminger
> >
> > Series
> > Acked-by: Neil Horman
>
> Use of rte_log would be better for init messages, but since the driver
> makes no diffe
On Sat, Feb 14, 2015 at 5:28 PM, Neil Horman wrote:
> On Sat, Feb 14, 2015 at 10:32:58AM -0500, Stephen Hemminger wrote:
> > Device driver should log via DPDK log, not to printf which is
> > sends to /dev/null in a daemon application.
> >
> > Signed-off-by: Stephen Hemminger
> > ---
> > lib/lib
On Sat, Feb 14, 2015 at 10:32:58AM -0500, Stephen Hemminger wrote:
> Device driver should log via DPDK log, not to printf which is
> sends to /dev/null in a daemon application.
>
> Signed-off-by: Stephen Hemminger
> ---
> lib/librte_pmd_enic/enic_compat.h | 11 +++
> 1 file changed, 7 in
Device driver should log via DPDK log, not to printf which is
sends to /dev/null in a daemon application.
Signed-off-by: Stephen Hemminger
---
lib/librte_pmd_enic/enic_compat.h | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/lib/librte_pmd_enic/enic_compat.h
b/li
4 matches
Mail list logo