From: Linus Walleij <linus.walleij@linaro.org>
To: chenguanxi11234@163.com
Cc: arnd@arndb.de, cgel.zte@gmail.com, chen.haonan2@zte.com.cn,
gregkh@linuxfoundation.org, jgg@ziepe.ca,
jiang.xuexin@zte.com.cn, jroedel@suse.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
rmk+kernel@armlinux.org.uk, rppt@kernel.org,
willy@infradead.org, yang.guang5@zte.com.cn
Subject: Re: [PATCH linux-next] ARM/dma-mapping: replace kzalloc() and vzalloc() with kvzalloc()
Date: Thu, 14 Dec 2023 14:17:51 +0100 [thread overview]
Message-ID: <CACRpkdb-pARMSCe_kugLOFriSrwuQVXJ3L+6TnsnmDNedowDRw@mail.gmail.com> (raw)
In-Reply-To: <20231213143954.2541-1-chenguanxi11234@163.com>
On Wed, Dec 13, 2023 at 3:41 PM <chenguanxi11234@163.com> wrote:
> >Looks good to me:
> >Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> >Please put this patch into Russell's patch tracker.
>
> Hello, I would like to ask, do you mean to have
> me CC the patch email to Russell?I don't really
> understand what patch tracker means.Thank you.
This is Russell's patch tracker:
https://www.armlinux.org.uk/developer/patches/
Create an account, read the help text, you can submit patches
using a web interface or through mail.
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-14 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 3:20 [PATCH linux-next] ARM/dma-mapping: replace kzalloc() and vzalloc() with kvzalloc() yang.guang5
2023-12-13 8:26 ` Linus Walleij
2023-12-13 14:39 ` chenguanxi11234
2023-12-14 13:17 ` Linus Walleij [this message]
2023-12-14 17:10 ` Russell King (Oracle)
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=CACRpkdb-pARMSCe_kugLOFriSrwuQVXJ3L+6TnsnmDNedowDRw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=arnd@arndb.de \
--cc=cgel.zte@gmail.com \
--cc=chen.haonan2@zte.com.cn \
--cc=chenguanxi11234@163.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=jiang.xuexin@zte.com.cn \
--cc=jroedel@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rppt@kernel.org \
--cc=willy@infradead.org \
--cc=yang.guang5@zte.com.cn \
/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).