From: 苏辉 <sh_def@163.com>
To: "Björn Töpel" <bjorn.topel@intel.com>
Cc: madalin.bucur@nxp.com, davem@davemloft.net, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
sfr@canb.auug.org.au
Subject: Re:Re: linux-next: ERROR: build error for arm64
Date: Sun, 6 Dec 2020 16:33:43 +0800 (CST) [thread overview]
Message-ID: <ea58b17.d87.176372f6ac3.Coremail.sh_def@163.com> (raw)
In-Reply-To: <a6899dcd-eee7-3559-6f4e-584f5f5973ce@intel.com>
At 2020-12-06 16:25:19, "Björn Töpel" <bjorn.topel@intel.com> wrote:
Ok, thanks.
prev parent reply other threads:[~2020-12-06 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201206073231.GA3805@rlk>
2020-12-06 8:25 ` Björn Töpel
2020-12-06 8:33 ` 苏辉 [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=ea58b17.d87.176372f6ac3.Coremail.sh_def@163.com \
--to=sh_def@163.com \
--cc=bjorn.topel@intel.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®