From: Jason Self <j@jxself.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Ben Hutchings <ben@decadent.org.uk>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH] make builddeb invoke calls to linux-update-symlink
Date: Fri, 22 May 2020 17:41:43 -0700 [thread overview]
Message-ID: <20200522174143.72ac4ddc@pc> (raw)
In-Reply-To: <CAK7LNAScfa9bqc3ViVX-+u3uJU=Zv_oWXCWdN6O_N_fw=AdQ5w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
On Sat, 23 May 2020 02:01:17 +0900
Masahiro Yamada <masahiroy@kernel.org> wrote:
> Hi Ben,
>
> On Sun, May 10, 2020 at 1:06 PM Jason Self <j@jxself.org> wrote:
> >
> > The official Debian kernel packages,
>
> I'd like to consult you.
> Does this patch look OK?
No. After submitting the patch I saw that I made a stupid mistake and
forgot to terminate one of the case statements and to use
/$installed_image_path instead of $installed_image_path so that it
provides the absolute path. I can resubmit it with those corrections
but have been waiting before doing so in case there is more feedback.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2020-05-23 0:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 4:06 [PATCH] make builddeb invoke calls to linux-update-symlink Jason Self
2020-05-22 17:01 ` Masahiro Yamada
2020-05-23 0:41 ` Jason Self [this message]
2020-05-23 1:14 ` Ben Hutchings
2020-05-23 20:38 ` [PATCH] make builddeb invoke calls to linux-update-symlinks Jason Self
2020-05-24 0:40 ` Ben Hutchings
-- strict thread matches above, loose matches on Subject: below --
2020-05-10 3:25 [PATCH] make builddeb invoke calls to linux-update-symlink Jason Self
2020-05-10 3:49 ` Jason Self
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=20200522174143.72ac4ddc@pc \
--to=j@jxself.org \
--cc=ben@decadent.org.uk \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@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.