All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rupesh Gujare <rupesh.gujare@atmel.com>
To: <devel@driverdev.osuosl.org>
Cc: <linux-kernel@vger.kernel.org>, <gregkh@linuxfoundation.org>
Subject: [PATCH 00/01] staging: ozwpan: Remove event tracing code
Date: Wed, 12 Jun 2013 14:00:51 +0100	[thread overview]
Message-ID: <1371042052-13463-1-git-send-email-rupesh.gujare@atmel.com> (raw)

This patch series removes event tracing code as it will be replaced by in-kernel
event tracing infrastructure.

http://permalink.gmane.org/gmane.linux.drivers.driver-project.devel/27606

Rupesh Gujare (1):
  staging: ozwpan: remove event tracing code.

 drivers/staging/ozwpan/Kbuild       |    3 +-
 drivers/staging/ozwpan/ozappif.h    |    2 -
 drivers/staging/ozwpan/ozcdev.c     |    5 -
 drivers/staging/ozwpan/ozconfig.h   |    1 -
 drivers/staging/ozwpan/ozevent.c    |  195 -----------------------------------
 drivers/staging/ozwpan/ozevent.h    |   32 ------
 drivers/staging/ozwpan/ozeventdef.h |   40 -------
 drivers/staging/ozwpan/ozhcd.c      |   47 ---------
 drivers/staging/ozwpan/ozmain.c     |    9 --
 drivers/staging/ozwpan/ozpd.c       |   23 +----
 drivers/staging/ozwpan/ozproto.c    |   17 ---
 drivers/staging/ozwpan/ozusbsvc.c   |    5 -
 drivers/staging/ozwpan/ozusbsvc1.c  |    5 -
 13 files changed, 4 insertions(+), 380 deletions(-)
 delete mode 100644 drivers/staging/ozwpan/ozevent.c
 delete mode 100644 drivers/staging/ozwpan/ozevent.h
 delete mode 100644 drivers/staging/ozwpan/ozeventdef.h

-- 
1.7.9.5


             reply	other threads:[~2013-06-12 13:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 13:00 Rupesh Gujare [this message]
2013-06-12 13:00 ` [PATCH 01/01] staging: ozwpan: remove event tracing code Rupesh Gujare

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1371042052-13463-1-git-send-email-rupesh.gujare@atmel.com \
    --to=rupesh.gujare@atmel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.