public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k <linux-m68k@lists.linux-m68k.org>,
	Tejun Heo <tj@kernel.org>, Jens Axboe <jens.axboe@oracle.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Fwd: [PATCH] [RFC] ataflop: remove buggy IRQ disable from do_fd_request()
Date: Mon, 19 Oct 2009 09:35:30 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.00.0910190932030.8582@wotan.suse.de> (raw)
In-Reply-To: <alpine.DEB.2.00.0910182126120.6395@zirkon.biophys.uni-duesseldorf.de>

On Sun, 18 Oct 2009, Michael Schmitz wrote:

> > The patch is not removing any locking. It only
> > 
> > 1) removes the local_irq_disable() that has been commented out for many 
> >    years already anyway
> > 2) removes the saving and restoring of CPU flags around do_fd_request(), 
> >    which is rather clearly a nop than any kind of "locking"
> > 
> > > > [1] http://lkml.org/lkml/2002/12/27/58
> > > > 
> > > > Signed-off-by: Jiri Kosina <jkosina@suse.cz>
> > > 
> > > NAck for my part. 
> > 
> > Please elaborate a little bit more which of the two points above you base 
> > your NACK on.
> 
> The removal of local_irq_disable() (which should have been local_irq_enable()) 
> just raised a flag, and I didn't immediately see why the interrupt enable had 
> been commented out. 

Yes, it has been commented out in a very non-intuitive way.

> With a bit of further thought on the matter I am satisfied that this patch will 
> not impact on driver function at all, and do not wish to sustain my objection.
> 
> IOW: Ack, and my sincere apologies for wasting your time. 

Thanks, I have added

	Acked-by: Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>

to the patch changelog in my tree.

-- 
Jiri Kosina
SUSE Labs, Novell Inc.

  reply	other threads:[~2009-10-19  7:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LSU.2.00.0910091141150.19284@wotan.suse.de>
2009-10-10  9:01 ` Fwd: [PATCH] [RFC] ataflop: remove buggy IRQ disable from do_fd_request() Geert Uytterhoeven
2009-10-11  7:01   ` Michael Schmitz
2009-10-12  7:58     ` Jens Axboe
2009-10-18  8:24       ` Michael Schmitz
2009-10-12  9:19     ` Jiri Kosina
     [not found]     ` <alpine.LSU.2.00.0910121106330.19284@wotan.suse.de>
2009-10-18 21:14       ` Michael Schmitz
2009-10-19  7:35         ` Jiri Kosina [this message]
2009-10-20  6:51           ` Michael Schmitz
     [not found]           ` <alpine.DEB.2.00.0910200847320.8658@zirkon.biophys.uni-duesseldorf.de>
2009-10-20  9:24             ` Andreas Schwab
2009-10-31  3:58               ` Michael Schmitz

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.LSU.2.00.0910190932030.8582@wotan.suse.de \
    --to=jkosina@suse.cz \
    --cc=geert@linux-m68k.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=schmitz@biophys.uni-duesseldorf.de \
    --cc=tj@kernel.org \
    /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