From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Murphy Zhou <jencce.kernel@gmail.com>
Cc: Linux-Next <linux-next@vger.kernel.org>, linuxppc-dev@lists.ozlabs.org
Subject: Re: linux-next tree panic on ppc64le
Date: Wed, 22 Feb 2023 19:21:24 +0700 [thread overview]
Message-ID: <d96f1c64-a82a-afde-0ecf-3b1dab6510a8@gmail.com> (raw)
In-Reply-To: <CADJHv_tzBWoGDBfNCsg-HKt8aKacXgmvY31mS47y30XkNyAw4w@mail.gmail.com>
On 2/22/23 16:13, Murphy Zhou wrote:
> next-20230221
>
> I'll try powerpc/next.
>
OK, but next time when you reply, don't top-post; reply inline
with appropriate context instead.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-02-22 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 0:55 linux-next tree panic on ppc64le Murphy Zhou
2023-02-22 2:35 ` Bagas Sanjaya
2023-02-22 9:13 ` Murphy Zhou
2023-02-22 12:21 ` Bagas Sanjaya [this message]
2023-02-22 23:52 ` Murphy Zhou
2023-02-23 5:10 ` Michael Ellerman
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=d96f1c64-a82a-afde-0ecf-3b1dab6510a8@gmail.com \
--to=bagasdotme@gmail.com \
--cc=jencce.kernel@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).