All of lore.kernel.org
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: dledford@redhat.com
Cc: kosaki.motohiro@jp.fujitsu.com, akpm@linux-foundation.org,
	kosaki.motohiro@gmail.com, linux-kernel@vger.kernel.org,
	amwang@redhat.com, jslaby@suse.cz, ebiederm@xmission.com,
	joe.korty@ccur.com, dhowells@redhat.com
Subject: Re: [resend][PATCH 1/3] mqueue: revert bump up DFLT_*MAX
Date: Mon, 19 Mar 2012 16:49:54 -0400	[thread overview]
Message-ID: <4F679BF2.7040107@jp.fujitsu.com> (raw)
In-Reply-To: <79ac1725-6aa2-4d67-8b59-cbf752ea9f3e@zmail13.collab.prod.int.phx2.redhat.com>

On 3/19/2012 2:16 PM, Doug Ledford wrote:
> ----- Original Message -----
>> On 3/14/2012 5:45 PM, Doug Ledford wrote:
>>> On 03/14/2012 05:38 PM, Andrew Morton wrote:
>>>> On Wed, 14 Mar 2012 17:28:33 -0400
>>>> Doug Ledford <dledford@redhat.com> wrote:
>>>>
>>>>> This has obviously fallen through the cracks.
>>>>
>>>> It sure has.  Please dig out whatever is the currently favored
>>>> patchset, refresh, retest and resend, with changelogging which
>>>> fully
>>>> covers the reasoning and decision process?
>>>
>>> OK, completely redoing patch set then against current Linus tree.
>>>
>>> Motohiro, would you be so kind as to resend my your patches that
>>> went on
>>> top of mine and I'll create a complete patch set?
>>
>> I'm sorry. I already have a rebased patch. but I haven't posted. I
>> have toa
>> hurry.
> 
> Actually, I already pulled them from the lkml archives and fixed up
> the one patch that didn't apply cleanly.  The only reason I haven't
> sent the entire patchset out yet is that I'm writing a test/verification
> app to go along with it.

OK, I'll stop this work then. Good luck. :)

But, please rebase the patch on top linux-next. It's more akpm happy and
you are going to see more conflicts. That's the reason why I thought I
need more tests.


      reply	other threads:[~2012-03-19 20:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 22:35 [resend][PATCH 1/3] mqueue: revert bump up DFLT_*MAX kosaki.motohiro
2011-12-09 22:35 ` [resend][PATCH 2/3] mqueue: don't use kmalloc with KMALLOC_MAX_SIZE kosaki.motohiro
2011-12-09 22:35 ` [resend][PATCH 3/3] mqueue: separate mqueue default value from maximum value kosaki.motohiro
2011-12-18 18:29 ` [resend][PATCH 1/3] mqueue: revert bump up DFLT_*MAX KOSAKI Motohiro
2011-12-18 18:29 ` KOSAKI Motohiro
2011-12-18 18:38   ` Andrew Morton
2012-03-14 21:28     ` Doug Ledford
2012-03-14 21:38       ` Andrew Morton
2012-03-14 21:45         ` Doug Ledford
2012-03-19 18:02           ` KOSAKI Motohiro
2012-03-19 18:16             ` Doug Ledford
2012-03-19 20:49               ` KOSAKI Motohiro [this message]

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=4F679BF2.7040107@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=amwang@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=dledford@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=joe.korty@ccur.com \
    --cc=jslaby@suse.cz \
    --cc=kosaki.motohiro@gmail.com \
    --cc=linux-kernel@vger.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 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.