All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, Len Brown <len.brown@intel.com>,
	"Luck, Tony" <tony.luck@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-ia64@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: [PATCH] IRQ resource deallocation[0/2]
Date: Wed, 08 Dec 2004 16:07:35 +0900	[thread overview]
Message-ID: <41B6A837.4030505@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0412070820240.13396@montezuma.fsmlabs.com>

Zwane Mwaikambo wrote:

> On Tue, 7 Dec 2004, Kenji Kaneshige wrote:
> 
>> I had posted the IRQ resource deallocation patch a couple of monthes
>> ago and I had incorporated all feedbacks from the mailing list
>> (http://marc.theaimsgroup.com/?l=linux-kernel&m=109688530703122&w=2).
>> But it doesn't seems to be included yet, so I would like to try again.
>> I hope my patch is included onto -mm tree since I want the patches
>> be tested by many people.
> 
> You should remove the config option and make it unconditional.
> 

I think you're right. I'll update the patch.

Thanks,
Kenji Kaneshige


WARNING: multiple messages have this Message-ID (diff)
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, Len Brown <len.brown@intel.com>,
	"Luck, Tony" <tony.luck@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-ia64@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: [PATCH] IRQ resource deallocation[0/2]
Date: Wed, 08 Dec 2004 07:07:35 +0000	[thread overview]
Message-ID: <41B6A837.4030505@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0412070820240.13396@montezuma.fsmlabs.com>

Zwane Mwaikambo wrote:

> On Tue, 7 Dec 2004, Kenji Kaneshige wrote:
> 
>> I had posted the IRQ resource deallocation patch a couple of monthes
>> ago and I had incorporated all feedbacks from the mailing list
>> (http://marc.theaimsgroup.com/?l=linux-kernel&m\x109688530703122&w=2).
>> But it doesn't seems to be included yet, so I would like to try again.
>> I hope my patch is included onto -mm tree since I want the patches
>> be tested by many people.
> 
> You should remove the config option and make it unconditional.
> 

I think you're right. I'll update the patch.

Thanks,
Kenji Kaneshige


  reply	other threads:[~2004-12-08  7:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-07  7:21 [PATCH] IRQ resource deallocation[0/2] Kenji Kaneshige
2004-12-07  7:21 ` Kenji Kaneshige
     [not found] ` <41B559DD.7040307-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2004-12-07 15:22   ` Zwane Mwaikambo
2004-12-07 15:22     ` Zwane Mwaikambo
2004-12-07 15:22     ` Zwane Mwaikambo
2004-12-08  7:07     ` Kenji Kaneshige [this message]
2004-12-08  7:07       ` Kenji Kaneshige
     [not found]     ` <Pine.LNX.4.61.0412070820240.13396-SOP5cCwKKQRMCHjbocvOOJqQE7yCjDx5@public.gmane.org>
2004-12-10  6:13       ` Kenji Kaneshige
2004-12-10  6:13         ` Kenji Kaneshige
2004-12-10  6:13         ` Kenji Kaneshige

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=41B6A837.4030505@jp.fujitsu.com \
    --to=kaneshige.kenji@jp.fujitsu.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --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 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.