lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1389462882.21727.36.camel@buesod1.americas.hpqcorp.net>
Date:	Sat, 11 Jan 2014 09:54:42 -0800
From:	Davidlohr Bueso <davidlohr@...com>
To:	Manfred Spraul <manfred@...orfullife.com>
Cc:	akpm@...ux-foundation.org, riel@...hat.com, aswin@...com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next 0/7] ipc: some misc updates & optimizations

On Sat, 2014-01-11 at 10:02 +0100, Manfred Spraul wrote:
> 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:

Just ignore that email, Andrew then applied (and fixed the merge
conflict) your whitespace cleanup patch and was already in linux-next by
the time I sent this patchset, so no need to worry/coordinate.

> 
> 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@...orfullife.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.

Thanks, I definitely want your ack/review for this one.

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ