All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wanlong Gao <wanlong.gao@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
	Pengfei Zhang <zoppof.zhang@gmail.com>,
	Linux PM mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] MIPS:i8259.c remove resume and shutdown to syscore_ops
Date: Wed, 25 May 2011 07:14:59 +0800	[thread overview]
Message-ID: <1306278899.2135.2.camel@Tux> (raw)
In-Reply-To: <201105242059.59770.rjw@sisk.pl>

On 二, 2011-05-24 at 20:59 +0200, Rafael J. Wysocki wrote:
> On Tuesday, May 24, 2011, Wanlong Gao wrote:
> > 
> > > On Tue, May 24, 2011 at 08:19:18PM +0800, Pengfei Zhang wrote:
> > > 
> > > > Remove the resume and shutdown of i8259A from the sysdev_class
> > > > to the syscore_ops since these members had removed from the
> > > > structure sysdev_class.
> > > 
> > > I don't see why one would want to want to first call
> > > register_syscore_ops
> > > then sysdev_class_register and sysdev_register?
> > > 
> > Hi Ralf:
> > If these not moved to syscore_ops, building will get error.
> > 
> > Hi Thomas:
> > Does you mean that we can just remove the sysfs entry now ?
> 
> I had the appended patch in my tree before the merge window started,
> but it conflicted with analogous changes in the MIPS tree, so I had
> dropped it.  Was it a mistake?
> 
> Rafael

Hi Rafael:

On 5/24/11, Ralf Baechle <ralf@linux-mips.org> wrote:
>Re: [PATCH] MIPS: Use struct syscore_ops instead of sysdevs for i8259
> On Fri, May 20, 2011 at 10:41:41PM +0900, Yoichi Yuasa wrote:
>
> Thanks, applied.
>
>   Ralf
It seems already applied some about this?

Thanks

Best regards
Wanlong Gao

  parent reply	other threads:[~2011-05-24 23:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 14:25 [PATCH] MIPS:i8259.c remove resume and shutdown to syscore_ops Wanlong Gao
2011-05-24 18:59 ` Rafael J. Wysocki
2011-05-24 18:59 ` Rafael J. Wysocki
2011-05-24 19:09   ` Manuel Lauss
2011-05-24 19:09   ` Manuel Lauss
2011-05-24 23:14   ` Wanlong Gao [this message]
2011-05-24 23:14   ` Wanlong Gao
  -- strict thread matches above, loose matches on Subject: below --
2011-05-24 12:19 Pengfei Zhang
2011-05-24 13:59 ` Ralf Baechle
2011-05-24 14:01   ` Thomas Gleixner

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=1306278899.2135.2.camel@Tux \
    --to=wanlong.gao@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=ralf@linux-mips.org \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    --cc=zoppof.zhang@gmail.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.