linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ritesh Harjani <riteshh@linux.ibm.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-ext4@vger.kernel.org, tytso@mit.edu
Cc: linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.com>,
	linux-kernel@vger.kernel.org, adilger.kernel@dilger.ca,
	sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	syzkaller-bugs@googlegroups.com,
	syzbot+82f324bb69744c5f6969@syzkaller.appspotmail.com
Subject: Re: [PATCHv5 1/1] ext4: mballoc: Use raw_cpu_ptr instead of this_cpu_ptr
Date: Wed, 3 Jun 2020 16:01:45 +0530	[thread overview]
Message-ID: <20200603103146.C42D65204F@d06av21.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <ca794804-7d99-9837-2490-366a2eb97a94@samsung.com>

> This fixes the warning observed on various Samsung Exynos SoC based
> boards with linux-next 20200602.
> 
> Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
> 

Thanks Marek,

Hello Ted,

Please pick up below change which I just sent with an added "Fixes" by
tag. Changes wise it is the same which Marek tested.

https://patchwork.ozlabs.org/project/linux-ext4/patch/20200603101827.2824-1-riteshh@linux.ibm.com/


-ritesh

  reply	other threads:[~2020-06-03 10:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 13:47 [PATCHv5 1/1] ext4: mballoc: Use raw_cpu_ptr instead of this_cpu_ptr Ritesh Harjani
2020-06-03 10:18 ` [PATCH " Ritesh Harjani
     [not found] ` <CGME20200603102422eucas1p109e0d0140e8fc61dc3e57957f2ccf700@eucas1p1.samsung.com>
2020-06-03 10:24   ` [PATCHv5 " Marek Szyprowski
2020-06-03 10:31     ` Ritesh Harjani [this message]
2020-06-09 10:57       ` Ritesh Harjani

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=20200603103146.C42D65204F@d06av21.portsmouth.uk.ibm.com \
    --to=riteshh@linux.ibm.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=sfr@canb.auug.org.au \
    --cc=syzbot+82f324bb69744c5f6969@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).