From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tejun Heo <tj@kernel.org>
Cc: Ryan Wilson <hap9@epoch.ncsc.mil>,
Jan Beulich <JBeulich@novell.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] xen-pcifront: don't use flush_scheduled_work()
Date: Mon, 24 Jan 2011 10:39:58 -0500 [thread overview]
Message-ID: <20110124153958.GA1222@dumpdata.com> (raw)
In-Reply-To: <20110124144303.GG11404@htj.dyndns.org>
On Mon, Jan 24, 2011 at 03:43:03PM +0100, Tejun Heo wrote:
> flush_scheduled_work() is scheduled for deprecation. Cancel ->op_work
2.6.39 or 2.6.40? Not seeing it referenced in feature-removal-schedule.txt file?
> directly instead.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Cc: Ryan Wilson <hap9@epoch.ncsc.mil>
> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Cc: Jan Beulich <JBeulich@novell.com>
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> ---
> drivers/pci/xen-pcifront.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> Index: work/drivers/pci/xen-pcifront.c
> ===================================================================
> --- work.orig/drivers/pci/xen-pcifront.c
> +++ work/drivers/pci/xen-pcifront.c
> @@ -733,8 +733,7 @@ static void free_pdev(struct pcifront_de
>
> pcifront_free_roots(pdev);
>
> - /*For PCIE_AER error handling job*/
Any reason for getting rid of the comment?
> - flush_scheduled_work();
> + cancel_work_sync(&pdev->op_work);
>
> if (pdev->irq >= 0)
> unbind_from_irqhandler(pdev->irq, pdev);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-24 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 14:43 [PATCH] xen-pcifront: don't use flush_scheduled_work() Tejun Heo
2011-01-24 15:39 ` Konrad Rzeszutek Wilk [this message]
2011-01-24 15:51 ` Tejun Heo
2011-01-24 15:52 ` Tejun Heo
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=20110124153958.GA1222@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@novell.com \
--cc=hap9@epoch.ncsc.mil \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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