From: Grant Likely <grant.likely@secretlab.ca>
To: Ben Dooks <ben@simtec.co.uk>
Cc: Axel Lin <axel.lin@gmail.com>,
linux-kernel@vger.kernel.org,
spi-devel-general@lists.sourceforge.net
Subject: Re: [PATCH] spi: tle620x: add missing device_remove_file()
Date: Thu, 26 May 2011 21:31:00 -0600 [thread overview]
Message-ID: <20110527033100.GL5032@ponder.secretlab.ca> (raw)
In-Reply-To: <4DCB9985.2050100@simtec.co.uk>
On Thu, May 12, 2011 at 09:25:41AM +0100, Ben Dooks wrote:
> On 11/05/11 13:39, Axel Lin wrote:
> >This patch includes below fixes:
> >1. Add missing device_remove_file for dev_attr_status_show in tle62x0_remove.
> >2. Fix tle62x0_probe error handling:
> > Currently, if the error happens when ptr> 0, gpio_attrs[0] is not
> > properly remove.
> >
> >Signed-off-by: Axel Lin<axel.lin@gmail.com>
> Acked-by: Ben Dooks <ben-linux@fluff.org>
Applied, thanks.
g.
prev parent reply other threads:[~2011-05-27 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 12:39 [PATCH] spi: tle620x: add missing device_remove_file() Axel Lin
2011-05-12 8:25 ` Ben Dooks
2011-05-27 3:31 ` Grant Likely [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=20110527033100.GL5032@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=axel.lin@gmail.com \
--cc=ben@simtec.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).