From: Nishad Kamdar <nishadkamdar@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Joe Perches <joe@perches.com>
Cc: NeilBrown <neil@brown.name>,
devel@driverdev.osuosl.org,
"Christian Lütke-Stetzkamp" <christian@lkamp.de>,
linux-kernel@vger.kernel.org, "John Crispin" <blogic@openwrt.org>,
"Dan Carpenter" <dan.carpenter@oracle.com>
Subject: Re: [PATCH v5 1/3] staging: mt7621-mmc: Remove #if 0 blocks
Date: Wed, 3 Oct 2018 21:51:58 +0530 [thread overview]
Message-ID: <20181003162153.GA19341@nishad> (raw)
In-Reply-To: <20181002221636.GA8586@kroah.com>
On Tue, Oct 02, 2018 at 03:16:36PM -0700, Greg Kroah-Hartman wrote:
> On Mon, Oct 01, 2018 at 08:13:40PM +0530, Nishad Kamdar wrote:
> > This patch removes #if 0 code blocks and usages of
> > functions defined in the #if 0 blocks.
> >
> > Signed-off-by: Nishad Kamdar <nishadkamdar@gmail.com>
> > ---
> > drivers/staging/mt7621-mmc/dbg.c | 21 +--
> > drivers/staging/mt7621-mmc/dbg.h | 14 --
> > drivers/staging/mt7621-mmc/sd.c | 269 -------------------------------
> > 3 files changed, 1 insertion(+), 303 deletions(-)
>
> This patch did not apply :(
Oh, do you mean it gave conflicts while applying?
I'll check and resubmit it in that case.
Thanks for the review.
regards,
Nishad
next prev parent reply other threads:[~2018-10-03 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 14:42 [PATCH v5 0/3] Remove #if 0 blocks and fix macros Nishad Kamdar
2018-10-01 14:43 ` [PATCH v5 1/3] staging: mt7621-mmc: Remove #if 0 blocks Nishad Kamdar
2018-10-02 22:16 ` Greg Kroah-Hartman
2018-10-03 16:21 ` Nishad Kamdar [this message]
2018-10-01 14:46 ` [PATCH v5 2/3] staging: mt7621-mmc: Remove single statement macro msdc_irq_restore() Nishad Kamdar
2018-10-01 14:48 ` [PATCH v5 3/3] staging: mt7621-mmc: Remove unused single statement macros Nishad Kamdar
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=20181003162153.GA19341@nishad \
--to=nishadkamdar@gmail.com \
--cc=blogic@openwrt.org \
--cc=christian@lkamp.de \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
/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.