From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] How to back-port upstream BSP patches to CIP kernel
Date: Wed, 30 Aug 2017 15:52:14 +0100 [thread overview]
Message-ID: <1504104734.2047.161.camel@codethink.co.uk> (raw)
In-Reply-To: <5aff707e-f641-4e1f-81c7-81669ae4c439@siemens.com>
On Wed, 2017-08-30 at 14:11 +0200, Jan Kiszka wrote:
> On 2017-08-30 09:59, Jan Kiszka wrote:
> > On 2017-08-18 20:31, Ben Hutchings wrote:
> >>
> >>> - the whole series of EFI capsule changes
> >>
> >> As this is all new stuff, I think it's OK. However you should remove
> >> the "default y" for EFI_CAPSULE_QUIRK_QUARK_CSH (upstream too!).
> >>
>
> Forgot to comment on this: We had this discussion during the merge, and
> the EFI maintainer accepted the point that this will only be enabled on
> 32-bit kernels that are potentially Quark-targeting. Plus, there are
> strong runtime measures that enable it only on Quark hardware. I would
> recommend to not deviate from this decision for CIP.
I agree that CIP shouldn't deviate.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
prev parent reply other threads:[~2017-08-30 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 14:59 [cip-dev] How to back-port upstream BSP patches to CIP kernel Jan Kiszka
2017-08-18 18:31 ` Ben Hutchings
2017-08-30 7:59 ` Jan Kiszka
2017-08-30 12:11 ` Jan Kiszka
2017-08-30 14:52 ` Ben Hutchings [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=1504104734.2047.161.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox