From: Jack Rosenthal <jrosenth@chromium.org>
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: linux-kernel@vger.kernel.org, chrome-platform@lists.linux.dev,
Stephen Boyd <swboyd@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Julius Werner <jwerner@chromium.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v6] firmware: google: Implement cbmem in sysfs driver
Date: Thu, 4 Aug 2022 07:31:20 -0700 [thread overview]
Message-ID: <YuvYOOvQqg424LoS@chromium.org> (raw)
In-Reply-To: <YuuBrUmiRYoaSmPw@google.com>
On 2022-08-04 at 08:22 +0000, Tzung-Bi Shih wrote:
> On Tue, Aug 02, 2022 at 07:03:43AM -0700, Jack Rosenthal wrote:
> > Link: https://issuetracker.google.com/239604743
>
> I doubt if the Link tag would be useful for public.
Thanks, made the bug public and kept the link.
> > Reported-by: kernel test robot <lkp@intel.com>
>
> Suggest to drop the Reported-by tag even if the robot reported some compile
> errors during the development. Given that the patch isn't a fixup but
> supporting something new (which isn't "reported by" the robot).
Done.
prev parent reply other threads:[~2022-08-04 14:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 9:56 htmldocs: Documentation/ABI/testing/sysfs-firmware-coreboot:2: WARNING: Definition list ends without a blank line; unexpected unindent kernel test robot
2022-08-01 15:26 ` [PATCH v5] firmware: google: Implement cbmem in sysfs driver Jack Rosenthal
2022-08-01 22:14 ` Julius Werner
2022-08-02 14:03 ` [PATCH v6] " Jack Rosenthal
2022-08-02 14:37 ` Guenter Roeck
2022-08-04 8:22 ` Tzung-Bi Shih
2022-08-04 14:28 ` [PATCH v7] " Jack Rosenthal
2022-08-04 20:59 ` Stephen Boyd
2022-08-04 23:14 ` Julius Werner
2022-08-10 16:40 ` Stephen Boyd
2022-08-10 22:26 ` Julius Werner
2022-08-10 23:58 ` Stephen Boyd
2022-08-11 1:17 ` Julius Werner
2022-08-06 20:46 ` Jack Rosenthal
2022-08-04 14:31 ` Jack Rosenthal [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=YuvYOOvQqg424LoS@chromium.org \
--to=jrosenth@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=swboyd@chromium.org \
--cc=tzungbi@kernel.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 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.