From: Ethan Sommer <e5ten.arch@gmail.com>
To: Borislav Petkov <bp@suse.de>
Cc: hpa@zytor.com, Jonathan Corbet <corbet@lwn.net>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Randy Dunlap <rdunlap@infradead.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Kees Cook <keescook@chromium.org>, Joe Perches <joe@perches.com>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Ingo Molnar <mingo@kernel.org>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Mark Rutland <mark.rutland@arm.com>,
John Stultz <john.stultz@linaro.org>,
Corey Minyard <cminyard@mvista.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] replace timeconst bc script with an sh script
Date: Thu, 20 Jun 2019 04:43:49 -0400 [thread overview]
Message-ID: <CAMEGPiqgoscn-20gDyrQOBYdbfzdimu91Dw0WLEjLKs+u5KSEA@mail.gmail.com> (raw)
In-Reply-To: <20190620082557.GB28346@zn.tnic>
(resend because I didn't know gmail would make it html)
Ah sorry about that, I accidentally replied to Kieran only instead of
to all, my response was "I will upload a patch with those issues fixed
shortly, in terms of the dependency as far as I know commands only required
for running tests don't count as kernel compilation dependencies, and I
don't see any other uses of bc except for Documentation/EDID/Makefile, so
I believe that bc can be removed from the kernel compilation section of the
process document and will include that change with the updated patch that
fixes the 2 issues you pointed out."
On Thu, Jun 20, 2019 at 4:26 AM Borislav Petkov <bp@suse.de> wrote:
>
> On Thu, Jun 20, 2019 at 04:11:32AM -0400, Ethan Sommer wrote:
> > removes the bc build dependency introduced when timeconst.pl was
> > replaced by timeconst.bc:
> > 70730bca1331 ("kernel: Replace timeconst.pl with a bc script")
>
> I don't see you answering Kieran's questions anywhere...
>
> --
> Regards/Gruss,
> Boris.
>
> SUSE Linux GmbH, GF: Felix Imendörffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2019-06-20 8:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 6:22 [PATCH] replace timeconst bc script with an sh script Ethan Sommer
2019-06-20 7:23 ` Kieran Bingham
2019-06-20 8:11 ` [PATCH v2] " Ethan Sommer
2019-06-20 8:25 ` Borislav Petkov
2019-06-20 8:43 ` Ethan Sommer [this message]
[not found] ` <CAMEGPiqk5TU=z2_wvMfPuihVc5zOLRrTSVCpLA23k0r-hmAzmg@mail.gmail.com>
2019-06-20 8:45 ` Borislav Petkov
2019-10-29 21:02 ` [PATCH v3] " Ethan Sommer
2019-10-30 11:37 ` Kieran Bingham
2019-10-30 16:26 ` Ethan Sommer
2019-11-02 20:54 ` hpa
2019-11-03 21:56 ` Ethan Sommer
2019-11-03 22:00 ` hpa
2019-11-03 23:57 ` Ethan Sommer
2019-11-04 3:03 ` hpa
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=CAMEGPiqgoscn-20gDyrQOBYdbfzdimu91Dw0WLEjLKs+u5KSEA@mail.gmail.com \
--to=e5ten.arch@gmail.com \
--cc=bp@suse.de \
--cc=cminyard@mvista.com \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=hpa@zytor.com \
--cc=joe@perches.com \
--cc=john.stultz@linaro.org \
--cc=keescook@chromium.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.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 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).