From: Michael Straube <straube.linux@gmail.com>
To: Martin Kaiser <martin@kaiser.cx>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
Pavel Skripkin <paskripkin@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] staging: r888eu: use dynamic allocation for efuse buffer
Date: Fri, 15 Jul 2022 08:02:56 +0200 [thread overview]
Message-ID: <be6d3fd0-566f-00ef-1404-830176d56e98@gmail.com> (raw)
In-Reply-To: <20220713075804.140986-1-martin@kaiser.cx>
Hi Martin,
just a typo in the subject line: r888eu
regards,
Michael
next prev parent reply other threads:[~2022-07-15 6:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 7:58 [PATCH] staging: r888eu: use dynamic allocation for efuse buffer Martin Kaiser
2022-07-13 10:24 ` Pavel Skripkin
2022-07-15 20:11 ` Martin Kaiser
2022-07-13 13:24 ` Larry Finger
2022-07-15 6:02 ` Michael Straube [this message]
2022-07-15 6:06 ` Michael Straube
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=be6d3fd0-566f-00ef-1404-830176d56e98@gmail.com \
--to=straube.linux@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--cc=paskripkin@gmail.com \
--cc=phil@philpotter.co.uk \
/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