From: Brian Norris <computersforpeace@gmail.com>
To: Prabhakar Lad <prabhakar.csengg@gmail.com>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: davinci_nand: Remove unnecessary labels from error path
Date: Mon, 20 Jan 2014 11:54:16 -0800 [thread overview]
Message-ID: <20140120195416.GU8919@ld-irv-0074> (raw)
In-Reply-To: <CA+V-a8sNSKX_W43G7A0zFKq1GX7k25XR2ZxVtxiQyAmLD5Rs4w@mail.gmail.com>
On Fri, Jan 17, 2014 at 01:20:36PM +0530, Prabhakar Lad wrote:
> On Fri, Jan 17, 2014 at 10:46 AM, Prabhakar Lad
> <prabhakar.csengg@gmail.com> wrote:
> > On Fri, Jan 17, 2014 at 3:02 AM, Brian Norris
> > <computersforpeace@gmail.com> wrote:
> >> On Wed, Jan 15, 2014 at 01:38:26PM +0530, Prabhakar Lad wrote:
> >>> From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
> >>>
> >>> This patch removes the unnecessary labels from
> >>> the error path in probe function which did nothing
> >>> than just returning error values, Thus simplifying code
> >>> path and improved readability.
> >>>
> >>> Signed-off-by: Lad, Prabhakar <prabhakar.csengg@gmail.com>
> >>
> >> This does not apply to my branch, since some OOM messages have been
> >> dropped. Can you rebase on l2-mtd.git (or linux-next)?
> >>
> > OK I'll rebase it against linux-next and post a v2.
> >
> My Bad was too late, there is already a patch fixing the above issue
> in linux-next
Ah, and my bad on remembering; I thought this looked familiar! :)
> please ignore this patch.
Sure.
Thanks,
Brian
prev parent reply other threads:[~2014-01-20 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 8:08 [PATCH] mtd: davinci_nand: Remove unnecessary labels from error path Prabhakar Lad
2014-01-16 21:32 ` Brian Norris
2014-01-17 5:16 ` Prabhakar Lad
2014-01-17 7:50 ` Prabhakar Lad
2014-01-20 19:54 ` Brian Norris [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=20140120195416.GU8919@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=prabhakar.csengg@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