From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Liu Shixin <liushixin2@huawei.com>
Cc: John Crispin <john@phrozen.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH 0/3] mips: use DEFINE_SHOW_ATTRIBUTE to simplify code
Date: Mon, 19 Sep 2022 16:46:37 +0200 [thread overview]
Message-ID: <20220919144637.GA7636@alpha.franken.de> (raw)
In-Reply-To: <20220913101038.1902389-1-liushixin2@huawei.com>
On Tue, Sep 13, 2022 at 06:10:35PM +0800, Liu Shixin wrote:
> Use DEFINE_SHOW_ATTRIBUTE to simplify code.
>
> Liu Shixin (3):
> mips: cavium: convert to DEFINE_SHOW_ATTRIBUTE
> mips: kernel: convert to DEFINE_SHOW_ATTRIBUTE
> mips: ralink: convert to DEFINE_SHOW_ATTRIBUTE
>
> arch/mips/cavium-octeon/oct_ilm.c | 17 +++--------------
> arch/mips/kernel/segment.c | 15 ++-------------
> arch/mips/ralink/bootrom.c | 15 ++-------------
> 3 files changed, 7 insertions(+), 40 deletions(-)
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-09-19 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 10:10 [PATCH 0/3] mips: use DEFINE_SHOW_ATTRIBUTE to simplify code Liu Shixin
2022-09-13 10:10 ` [PATCH 1/3] mips: cavium: convert to DEFINE_SHOW_ATTRIBUTE Liu Shixin
2022-09-13 10:10 ` [PATCH 2/3] mips: kernel: " Liu Shixin
2022-09-13 10:10 ` [PATCH 3/3] mips: ralink: " Liu Shixin
2022-09-19 14:46 ` Thomas Bogendoerfer [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=20220919144637.GA7636@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=wangkefeng.wang@huawei.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;
as well as URLs for NNTP newsgroup(s).