From: Vineet Gupta <vineet.gupta@linux.dev>
To: Sergey Matyukevich <geomatsi@gmail.com>
Cc: linux-snps-arc@lists.infradead.org,
Vladimir Isaev <isaev@synopsys.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [RFC PATCH 0/3] arc: remove CONFIG_SET_FS
Date: Thu, 17 Feb 2022 20:03:45 -0800 [thread overview]
Message-ID: <2c22b380-2a11-9d19-2cb8-18630478c09c@linux.dev> (raw)
In-Reply-To: <YgwVUmMlASsW7mSd@curiosity>
> IIUC it makes sense to drop this patch series from your for-next branch.
> These changes have been superseded by generic approach posted by
> Arnd Bergmann, see:
> https://lore.kernel.org/linux-arch/CAHk-=whXYWoP6of7js=f4zov62on97mNFRSVRWhY75WoGM6CoQ@mail.gmail.com/T/#t
>
> I tested patches by Arnd on ARC700/ARCHS platforms, so far so good.
Yep I've been following that thread and have dropped your ARC patchset.
Thx for testing. You can reply to Arnd with a
Tested-by: < your-name> #arc
-Vineet
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
prev parent reply other threads:[~2022-02-18 4:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 14:55 [RFC PATCH 0/3] arc: remove CONFIG_SET_FS Sergey Matyukevich
2022-02-01 14:55 ` [RFC PATCH 1/3] arc: use BUILD_BUG for invalid sizes in get_user/put_user Sergey Matyukevich
2022-02-01 15:08 ` Christoph Hellwig
2022-02-01 14:55 ` [RFC PATCH 2/3] arc: provide __{get,put}_kernel_nofault Sergey Matyukevich
2022-02-01 15:10 ` Christoph Hellwig
2022-02-01 14:55 ` [RFC PATCH 3/3] arc: remove set_fs() Sergey Matyukevich
2022-02-01 15:11 ` Christoph Hellwig
2022-02-02 5:14 ` [RFC PATCH 0/3] arc: remove CONFIG_SET_FS Vineet Gupta
2022-02-15 21:04 ` Sergey Matyukevich
2022-02-18 4:03 ` 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=2c22b380-2a11-9d19-2cb8-18630478c09c@linux.dev \
--to=vineet.gupta@linux.dev \
--cc=geomatsi@gmail.com \
--cc=hch@lst.de \
--cc=isaev@synopsys.com \
--cc=linux-snps-arc@lists.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