From: "Madhusudhan Chikkature" <madhu.cr@ti.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: tony@atomide.com, johnpol@2ka.mipt.ru, felipe.balbi@nokia.com,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 7/9]HDQ driver:replace semaphore with mutex
Date: Wed, 24 Sep 2008 18:47:10 +0530 [thread overview]
Message-ID: <024c01c91e47$dbdffa50$LocalHost@wipultra1303> (raw)
In-Reply-To: 5A47E75E594F054BAF48C5E4FC4B92AB02D5DC8C55@dbde02.ent.ti.com
----- Original Message -----
From: "Gadiyar, Anand" <gadiyar@ti.com>
To: "Chikkature Rajashekar, Madhusudhan" <madhu.cr@ti.com>; <felipe.balbi@nokia.com>
Cc: <tony@atomide.com>; <johnpol@2ka.mipt.ru>; <felipe.balbi@nokia.com>; <linux-omap@vger.kernel.org>
Sent: Wednesday, September 24, 2008 6:35 PM
Subject: RE: [PATCH 7/9]HDQ driver:replace semaphore with mutex
> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org On Behalf Of Chikkature Rajashekar, Madhusudhan
> ----- Original Message ----- From: "Felipe Balbi" <felipe.balbi@nokia.com>
>
> > On Wed, Sep 24, 2008 at 05:01:27PM +0530, ext Madhusudhan Chikkature wrote:
> >> From: Madhusudhan Chikkature<madhu.cr@ti.com>
> >>
> >> This patch replaces the usage of semaphore by mutex.
> >>
> >> Signed-off-by: Madhusudhan Chikkature<madhu.cr@ti.com>
> >> ---
> >> drivers/w1/masters/omap_hdq.c | 42 ++++++++++++++++++++++--------------------
> >> 1 files changed, 22 insertions(+), 20 deletions(-)
> >>
> >> Index: linux-omap-2.6/drivers/w1/masters/omap_hdq.c
> >> ===================================================================
> >> --- linux-omap-2.6.orig/drivers/w1/masters/omap_hdq.c 2008-09-24 11:13:12.000000000 +0530
> >> +++ linux-omap-2.6/drivers/w1/masters/omap_hdq.c 2008-09-24 11:49:45.000000000 +0530
> >> @@ -55,7 +55,7 @@ static int w1_id;
> >> struct hdq_data {
> >> struct device *dev;
> >> void __iomem *hdq_base;
> >> - struct semaphore hdq_semlock;
> >> + struct mutex hdq_mutex;
> >> int hdq_usecount;
> >> struct clk *hdq_ick;
> >> struct clk *hdq_fck;
> >
> > Please, fix these two:
> >
> > CHECK: struct mutex definition without comment
> > #58: FILE: w1/masters/omap_hdq.c:58:
> > + struct mutex hdq_mutex;
> >
> > CHECK: spinlock_t definition without comment
> > #63: FILE: w1/masters/omap_hdq.c:63:
> > + spinlock_t hdq_spinlock;
> >
> > total: 0 errors, 0 warnings, 2 checks, 732 lines checked
>
> I dont see any such checks reported by checkpatch.pl?
>
Oh, I guess Felipe uses `checkpatch.pl --strict`, right Felipe?
Hi,
Yes. That seems to be the case. I will add a couple of simple comments. I will send a final patch (patch #10)which will fix these minor things which Filipe reported.I do not want to rebase any of my patches again :)
Regards,
Madhu
- Anand
next prev parent reply other threads:[~2008-09-24 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 11:31 [PATCH 7/9]HDQ driver:replace semaphore with mutex Madhusudhan Chikkature
2008-09-24 11:50 ` Felipe Balbi
2008-09-24 13:00 ` Madhusudhan Chikkature
2008-09-24 13:05 ` Gadiyar, Anand
2008-09-24 13:17 ` Madhusudhan Chikkature [this message]
2008-09-24 23:01 ` Felipe Balbi
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='024c01c91e47$dbdffa50$LocalHost@wipultra1303' \
--to=madhu.cr@ti.com \
--cc=felipe.balbi@nokia.com \
--cc=gadiyar@ti.com \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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.