linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vineet Gupta <vineet.gupta1@synopsys.com>
To: Vineet Gupta <vineet.gupta1@synopsys.com>,
	<linux-kernel@vger.kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-snps-arc@lists.infradead.org>, <linux-mm@kvack.org>,
	<peterz@infradead.org>, <mark.rutland@arm.com>
Subject: Re: [PATCH v2 0/3] Replace opencoded set_mask_bits
Date: Fri, 8 Feb 2019 10:11:47 -0800	[thread overview]
Message-ID: <c8f00c90-2e09-e825-1a1f-056294cafbea@synopsys.com> (raw)
In-Reply-To: <1548275584-18096-1-git-send-email-vgupta@synopsys.com>

On 1/23/19 12:33 PM, Vineet Gupta wrote:
> Hi,
> 
> Repost of [1] rebased on 5.0-rc3 + accumulated Acked-by/Reviewed-by.
> No code changes since v1.
> 
> Please consider applying.
> 
> [1] http://lists.infradead.org/pipermail/linux-snps-arc/2019-January/005201.html
> 
> Thx,
> -Vineet

Ping ! @Peter, @Arnd are you happy with this. If so, Andrew can you please add
this via mm tree or do i need to pester the respective maintainers !

Thx,
-Vineet

> 
> Vineet Gupta (3):
>   coredump: Replace opencoded set_mask_bits()
>   fs: inode_set_flags() replace opencoded set_mask_bits()
>   bitops.h: set_mask_bits() to return old value
> 
>  fs/exec.c              | 7 +------
>  fs/inode.c             | 8 +-------
>  include/linux/bitops.h | 2 +-
>  3 files changed, 3 insertions(+), 14 deletions(-)
> 


      parent reply	other threads:[~2019-02-08 18:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 20:33 Vineet Gupta
2019-01-23 20:33 ` Vineet Gupta
2019-01-23 20:33 ` [PATCH v2 1/3] coredump: Replace opencoded set_mask_bits() Vineet Gupta
2019-01-23 20:33   ` Vineet Gupta
2019-01-23 20:33 ` [PATCH v2 2/3] fs: inode_set_flags() replace " Vineet Gupta
2019-01-23 20:33   ` Vineet Gupta
2019-01-23 20:33 ` [PATCH v2 3/3] bitops.h: set_mask_bits() to return old value Vineet Gupta
2019-01-23 20:33   ` Vineet Gupta
2019-02-08 18:11 ` Vineet Gupta [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=c8f00c90-2e09-e825-1a1f-056294cafbea@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox