From: Julia Lawall <julia.lawall@lip6.fr>
To: Shraddha Barke <shraddha.6596@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v2 0/2] Staging: Remove unused header files
Date: Fri, 30 Oct 2015 15:04:10 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.10.1510301504000.2364@hadrien> (raw)
In-Reply-To: <1446213783-30267-1-git-send-email-shraddha.6596@gmail.com>
On Fri, 30 Oct 2015, Shraddha Barke wrote:
> These patches remove unused header files
>
> Changes in v2-
> Made commit message clearer
They look better, thanks.
julia
> Shraddha Barke (2):
> Staging: sm750fb: Remove unused modedb.h file
> Staging: dgnc: Remove unused #include header file
>
> drivers/staging/dgnc/dgnc_utils.c | 1 -
> drivers/staging/sm750fb/modedb.h | 233 --------------------------------------
> drivers/staging/sm750fb/sm750.c | 2 -
> 3 files changed, 236 deletions(-)
> delete mode 100644 drivers/staging/sm750fb/modedb.h
>
> --
> 2.1.4
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/1446213783-30267-1-git-send-email-shraddha.6596%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>
prev parent reply other threads:[~2015-10-30 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 14:03 [PATCH v2 0/2] Staging: Remove unused header files Shraddha Barke
2015-10-30 14:03 ` [PATCH v2 1/2] Staging: sm750fb: Remove unused modedb.h file Shraddha Barke
2015-10-31 6:56 ` [Outreachy kernel] " Sudip Mukherjee
2015-10-30 14:03 ` [PATCH v2 2/2] Staging: dgnc: Remove unused #include header file Shraddha Barke
2015-10-30 14:04 ` Julia Lawall [this message]
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=alpine.DEB.2.10.1510301504000.2364@hadrien \
--to=julia.lawall@lip6.fr \
--cc=outreachy-kernel@googlegroups.com \
--cc=shraddha.6596@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 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.