From: Sudeep Holla <sudeep.holla@arm.com>
To: sean yang <seanyang230@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, sudeep.holla@arm.com,
cristian.marussi@arm.com
Subject: Re: Fwd: [PATCH] firmware: arm_scmi: Remove inappropriate error log.
Date: Thu, 2 Nov 2023 11:08:42 +0000 [thread overview]
Message-ID: <20231102110842.GB1391942@bogus> (raw)
In-Reply-To: <CADGqjF+qsrKcNntO7FdcUxJ+L4rC8jcMT94nv8uOOTH-VwG9mw@mail.gmail.com>
On Thu, Nov 02, 2023 at 05:55:37PM +0800, sean yang wrote:
> ---------- Forwarded message ---------
> 发件人： xinglong.yang <seanyang230@gmail.com>
> Date: 2023年11月1日周三 16:17
> Subject: [PATCH] firmware: arm_scmi: Remove inappropriate error log.
> To: <xinglong.yang@cixtech.com>, <sudeep.holla@arm.com>,
> <cristian.marussi@arm.com>
> Cc: <linux-arm-kernel@lists.infradead.org>
>
Same here, please avoid forwarding patches/emails on the list and wait
for couple of days to *resend*(not forward) the email/patch if you
suspect it wasn't delivered.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com>
To: sean yang <seanyang230@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, sudeep.holla@arm.com,
cristian.marussi@arm.com
Subject: Re: Fwd: [PATCH] firmware: arm_scmi: Remove inappropriate error log.
Date: Thu, 2 Nov 2023 11:08:42 +0000 [thread overview]
Message-ID: <20231102110842.GB1391942@bogus> (raw)
In-Reply-To: <CADGqjF+qsrKcNntO7FdcUxJ+L4rC8jcMT94nv8uOOTH-VwG9mw@mail.gmail.com>
On Thu, Nov 02, 2023 at 05:55:37PM +0800, sean yang wrote:
> ---------- Forwarded message ---------
> 发件人： xinglong.yang <seanyang230@gmail.com>
> Date: 2023年11月1日周三 16:17
> Subject: [PATCH] firmware: arm_scmi: Remove inappropriate error log.
> To: <xinglong.yang@cixtech.com>, <sudeep.holla@arm.com>,
> <cristian.marussi@arm.com>
> Cc: <linux-arm-kernel@lists.infradead.org>
>
Same here, please avoid forwarding patches/emails on the list and wait
for couple of days to *resend*(not forward) the email/patch if you
suspect it wasn't delivered.
--
Regards,
Sudeep
next prev parent reply other threads:[~2023-11-02 11:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 8:17 [PATCH] firmware: arm_scmi: Remove inappropriate error log xinglong.yang
2023-11-02 9:55 ` Fwd: " sean yang
2023-11-02 9:55 ` sean yang
2023-11-02 11:08 ` Sudeep Holla [this message]
2023-11-02 11:08 ` Sudeep Holla
2023-11-02 11:16 ` Sudeep Holla
2023-11-02 11:25 ` Cristian Marussi
2023-11-02 11:42 ` sean yang
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=20231102110842.GB1391942@bogus \
--to=sudeep.holla@arm.com \
--cc=cristian.marussi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanyang230@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.