All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Andrew Morton <akpm@osdl.org>
Cc: len.brown@intel.com, tony.luck@intel.com, greg@kroah.com,
	acpi-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org,
	pcihpd-discuss@lists.sourceforge.net
Subject: Re: [RFC/PATCH 0/3] ACPI based I/O APIC hot-plug
Date: Tue, 26 Apr 2005 19:20:10 +0900	[thread overview]
Message-ID: <426E15DA.9030800@jp.fujitsu.com> (raw)
In-Reply-To: <20050426025716.142c5726.akpm@osdl.org>

Andrew Morton wrote:
> "Kenji Kaneshige" <kaneshige.kenji@jp.fujitsu.com> wrote:
> 
>>Here is a set of patches to support ACPI based I/O APIC hotplug.
> 
> 
> OK, with the help of Tony's git tree I managed to get those merged up.
> 

Wow, great!
But I'm now updating these patches based on the feedbacks.
How should I do about this? Should I send these updates as
another cleanup patch?


> In future, please avoid sending multiple patches with the same Subject:? 
> Because when you do that I have to invent unique names for the patches and
> you don't know what those names were, so things get confusing.  See
> http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt for more, thanks.
> 

Sorry about that.
I'll see this.

Thanks,
Kenji Kaneshige
 

WARNING: multiple messages have this Message-ID (diff)
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Andrew Morton <akpm@osdl.org>
Cc: len.brown@intel.com, tony.luck@intel.com, greg@kroah.com,
	acpi-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org,
	pcihpd-discuss@lists.sourceforge.net
Subject: Re: [RFC/PATCH 0/3] ACPI based I/O APIC hot-plug
Date: Tue, 26 Apr 2005 10:20:10 +0000	[thread overview]
Message-ID: <426E15DA.9030800@jp.fujitsu.com> (raw)
In-Reply-To: <20050426025716.142c5726.akpm@osdl.org>

Andrew Morton wrote:
> "Kenji Kaneshige" <kaneshige.kenji@jp.fujitsu.com> wrote:
> 
>>Here is a set of patches to support ACPI based I/O APIC hotplug.
> 
> 
> OK, with the help of Tony's git tree I managed to get those merged up.
> 

Wow, great!
But I'm now updating these patches based on the feedbacks.
How should I do about this? Should I send these updates as
another cleanup patch?


> In future, please avoid sending multiple patches with the same Subject:? 
> Because when you do that I have to invent unique names for the patches and
> you don't know what those names were, so things get confusing.  See
> http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt for more, thanks.
> 

Sorry about that.
I'll see this.

Thanks,
Kenji Kaneshige
 

  reply	other threads:[~2005-04-26 10:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 13:39 [RFC/PATCH 0/3] ACPI based I/O APIC hot-plug Kenji Kaneshige
2005-04-21 13:39 ` Kenji Kaneshige
2005-04-26  9:57 ` Andrew Morton
2005-04-26  9:57   ` Andrew Morton
2005-04-26 10:20   ` Kenji Kaneshige [this message]
2005-04-26 10:20     ` Kenji Kaneshige
2005-04-26 10:35     ` Andrew Morton
2005-04-26 10:35       ` Andrew Morton
2005-04-26 15:07       ` Kenji Kaneshige
2005-04-26 15:07         ` Kenji Kaneshige
2005-04-26 14:03 ` Paul Ionescu
2005-04-26 14:03   ` Paul Ionescu
     [not found]   ` <pan.2005.04.26.14.03.23.413590-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
2005-04-26 14:34     ` Kenji Kaneshige
2005-04-26 14:34       ` [ACPI] " 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=426E15DA.9030800@jp.fujitsu.com \
    --to=kaneshige.kenji@jp.fujitsu.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=len.brown@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    --cc=tony.luck@intel.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.