From: Greg KH <greg@kroah.com>
To: Sergio Luis <sergio@uece.br>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
Mathieu Segaud <mathieu.segaud@regala.cx>,
linux-pci@atrey.karlin.mff.cuni.cz,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/1] PCI: change procfs interface to use unlocked_ioctl
Date: Fri, 11 Jan 2008 22:36:51 +0000 [thread overview]
Message-ID: <20080111223651.GA5942@kroah.com> (raw)
In-Reply-To: <4786E1CE.4080404@uece.br>
On Fri, Jan 11, 2008 at 12:26:06AM -0300, Sergio Luis wrote:
> Change drivers/pci/proc.c to use the unlocked_ioctl handler instead of
> the ioctl one.
Thanks, but Mathieu Segaud <mathieu.segaud@regala.cx> just beat you to
this by a few hours with a patch he sent me :)
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Sergio Luis <sergio@uece.br>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
Mathieu Segaud <mathieu.segaud@regala.cx>,
linux-pci@atrey.karlin.mff.cuni.cz,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/1] PCI: change procfs interface to use unlocked_ioctl instead of ioctl
Date: Fri, 11 Jan 2008 14:36:51 -0800 [thread overview]
Message-ID: <20080111223651.GA5942@kroah.com> (raw)
In-Reply-To: <4786E1CE.4080404@uece.br>
On Fri, Jan 11, 2008 at 12:26:06AM -0300, Sergio Luis wrote:
> Change drivers/pci/proc.c to use the unlocked_ioctl handler instead of
> the ioctl one.
Thanks, but Mathieu Segaud <mathieu.segaud@regala.cx> just beat you to
this by a few hours with a patch he sent me :)
greg k-h
next prev parent reply other threads:[~2008-01-11 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 3:26 [PATCH 1/1] PCI: change procfs interface to use unlocked_ioctl instead Sergio Luis
2008-01-11 3:26 ` [PATCH 1/1] PCI: change procfs interface to use unlocked_ioctl instead of ioctl Sergio Luis
2008-01-11 22:36 ` Greg KH [this message]
2008-01-11 22:36 ` Greg KH
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=20080111223651.GA5942@kroah.com \
--to=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mathieu.segaud@regala.cx \
--cc=sergio@uece.br \
/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.