mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Li Shaohua <shaohua.li@intel.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Grzegorz Kulewski <kangur@polcom.net>,
	Zwane Mwaikambo <zwane@arm.linux.org.uk>,
	Andrew Morton <akpm@osdl.org>,
	ACPI List <acpi-devel@lists.sourceforge.net>,
	lkml <linux-kernel@vger.kernel.org>,
	Len Brown <len.brown@intel.com>
Subject: Re: [ACPI] Re: Fw: Anybody? 2.6.11 (stable and -rc) ACPI breaks USB
Date: Wed, 23 Mar 2005 08:54:09 +0800	[thread overview]
Message-ID: <1111539249.18927.17.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <41062.15.99.19.46.1111525073.squirrel@mail.atl.hp.com>

On Wed, 2005-03-23 at 04:57, Bjorn Helgaas wrote:
> > Your patch applied with some problems:
> >
> > patching file arch/i386/pci/irq.c
> > Hunk #2 succeeded at 1081 with fuzz 2 (offset 1 line).
> > patching file drivers/acpi/pci_irq.c
> > patching file drivers/pci/quirks.c
> > Hunk #1 succeeded at 678 (offset -5 lines).
> 
> These indicate minor differences in these files between upstream BK
> (which is what my patch was against) and the kernel you're building.
> You can ignore them.
> 
> > Then I tested it and it works (at least my speedtouch still works).
> 
> Great.  Shaohua, where should we go from here?  Do you have more
> concerns with the current patch, or should we ask Andrew to put it
> in -mm?  If you do have concerns, would you like to propose an
> alternate patch that fixes the problem for Grzegorz?
No, the patch is great to me.

Thanks,
Shaohua


  reply	other threads:[~2005-03-23  1:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050304234622.63e8a335.akpm@osdl.org>
2005-03-10 23:08 ` Grzegorz Kulewski
2005-03-11 16:48   ` [ACPI] " Bjorn Helgaas
2005-03-11 19:36     ` Grzegorz Kulewski
2005-03-11 20:56       ` Bjorn Helgaas
2005-03-11 21:47         ` Grzegorz Kulewski
2005-03-11 22:29           ` Bjorn Helgaas
2005-03-12  0:13             ` Grzegorz Kulewski
2005-03-13 15:14             ` Grzegorz Kulewski
2005-03-15 19:35               ` Bjorn Helgaas
2005-03-15 23:02                 ` Zwane Mwaikambo
2005-03-16 16:10                   ` Bjorn Helgaas
2005-03-17  1:33                     ` Li Shaohua
2005-03-17 18:08                       ` Bjorn Helgaas
2005-03-18  1:09                         ` Li Shaohua
2005-03-18 18:07                           ` Bjorn Helgaas
2005-03-21 16:33                             ` Bjorn Helgaas
2005-03-21 23:33                               ` Grzegorz Kulewski
2005-03-22 20:57                                 ` Bjorn Helgaas
2005-03-23  0:54                                   ` Li Shaohua [this message]
2005-03-23  3:57                                     ` Bjorn Helgaas
2005-03-23 18:40                                       ` Len Brown
2005-03-24 18:24                                         ` Bjorn Helgaas
2005-03-25 19:07                                           ` Len Brown
2005-03-14  9:30 Li, Shaohua

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=1111539249.18927.17.camel@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=kangur@polcom.net \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@arm.linux.org.uk \
    /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

all inboxes | Powered by JetHome®