mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Davidlohr Bueso <davidlohr@hp.com>, akpm@linux-foundation.org
Cc: riel@redhat.com, aswin@hp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next 0/7] ipc: some misc updates & optimizations
Date: Sat, 11 Jan 2014 10:02:55 +0100	[thread overview]
Message-ID: <52D108BF.8060401@colorfullife.com> (raw)
In-Reply-To: <1389379707-20298-1-git-send-email-davidlohr@hp.com>

Hi David,

On 01/10/2014 07:48 PM, Davidlohr Bueso wrote:
> A few updates to the ipc code, mostly some very needed cleanups (yes, we still
> have loads more to do, but it's a start). Nothing particularly interesting,
> except perhaps for the last two patches, which include a locking optimization
> and barrier documentation for message queues. Absolutely no functional changes.
>
> Applies on top of linux-next +  Manfred's 'whitespace cleanup' patch. Tested
> with LTP.
Now you confuse me.
In your other mail, you write that my patch doesn't apply to linux-next:

On 01/07/2014 06:12 PM, Davidlohr Bueso wrote:
> This patch doesn't apply on top of linux-next (which now includes 
> Rafael's changes), could you please resend? I'm planning some more 
> cleanups on top of this so, if Andrew agrees, I can include these 
> changes to my patchset. Thanks, Davidlohr 

Perhaps: Could you include (and update, if required) my patch into your 
patchset?
It's probably simpler if we have only one set of ipc cleanups around.

> Thanks!
>
> Davidlohr Bueso (7):
>    ipc: standardize code comments
>    ipc: remove braces for single statements
>    ipc: remove useless return statement
>    ipc: simplify sysvipc_proc_open return
>    ipc: delete seq_max field in struct ipc_ids
Acked-by: Manfred Spraul <manfred@colorfullife.com>
>    ipc: share ids rwsem when possible in ipcget_public
This patch is a real change. Could you at least make it the last one in 
the series?
I will try to review it, but I don't know yet when I will find the time.

>    ipc,msg: document barriers
Acked-by: Manfred Spraul <manfred@colorfullife.com>

--
     Manfred

  parent reply	other threads:[~2014-01-11  9:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 18:48 Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 1/7] ipc: standardize code comments Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 2/7] ipc: remove braces for single statements Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 3/7] ipc: remove useless return statement Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 4/7] ipc: simplify sysvipc_proc_open return Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 5/7] ipc: delete seq_max field in struct ipc_ids Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 6/7] ipc: share ids rwsem when possible in ipcget_public Davidlohr Bueso
2014-01-10 18:48 ` [PATCH 7/7] ipc,msg: document barriers Davidlohr Bueso
2014-01-11  4:18   ` Mike Galbraith
2014-01-11  9:02 ` Manfred Spraul [this message]
2014-01-11 17:54   ` [PATCH -next 0/7] ipc: some misc updates & optimizations Davidlohr Bueso

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=52D108BF.8060401@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=akpm@linux-foundation.org \
    --cc=aswin@hp.com \
    --cc=davidlohr@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome