public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Seunghun Lee <waydi1@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Lidza Louina <lidza.louina@gmail.com>,
	Mark Hounschell <markh@compro.net>
Subject: Re: [PATCH] staging: dgnc: remove DPR Macros and related codes.
Date: Fri, 15 Aug 2014 14:08:41 +0800	[thread overview]
Message-ID: <20140815060841.GA28534@kroah.com> (raw)
In-Reply-To: <1407850214-3678-1-git-send-email-waydi1@gmail.com>

On Tue, Aug 12, 2014 at 10:30:14PM +0900, Seunghun Lee wrote:
> In dgnc_drivers.h, DPR macro and DPR_* macros are defined but do nothing.
> 
> So remove them and related codes.
> 
> CC: Lidza Louina <lidza.louina@gmail.com>
> CC: Mark Hounschell <markh@compro.net>
> Signed-off-by: Seunghun Lee <waydi1@gmail.com>
> ---
>  drivers/staging/dgnc/dgnc_cls.c    |   63 +--------
>  drivers/staging/dgnc/dgnc_driver.c |   20 +--
>  drivers/staging/dgnc/dgnc_driver.h |   21 ---
>  drivers/staging/dgnc/dgnc_mgmt.c   |   23 ----
>  drivers/staging/dgnc/dgnc_neo.c    |  104 ++-------------
>  drivers/staging/dgnc/dgnc_tty.c    |  249 +++---------------------------------
>  6 files changed, 36 insertions(+), 444 deletions(-)

This conflicts with patches others have sent, can you refresh it after
next Tuesday or so when I catch up with the pending patches and can push
them out?

thanks,

greg k-h

  reply	other threads:[~2014-08-15 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12 13:30 [PATCH] staging: dgnc: remove DPR Macros and related codes Seunghun Lee
2014-08-15  6:08 ` Greg KH [this message]
2014-08-15 16:56   ` Seunghun Lee
  -- strict thread matches above, loose matches on Subject: below --
2014-08-19 15:30 Seunghun Lee

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=20140815060841.GA28534@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=lidza.louina@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.net \
    --cc=waydi1@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox