public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Do you still need ~/src/patches/arm-dont-require-distutils.patch and ~/src/patches/arm-multi-grsec-compile-fixes.patch ?
Date: Fri, 21 May 2021 10:25:30 +0100	[thread overview]
Message-ID: <100F2D11-0233-45AE-81A5-CB2F038B4D54@ipfire.org> (raw)
In-Reply-To: <0178b685-3a82-51fb-14b3-5e0d5e587e58@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

You can run an ARM build and see if stuff breaks.

If it breaks on the nightly builders you will owe me a bottle of something nice :)

-Michael

> On 21 May 2021, at 10:24, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Hello Michael,
> 
> thanks for your reply.
> 
>> Hello,
>> 
>> If they are not referenced in an lfs file we don’t need them any more.
> 
> Well, since I never really understood what magic Arne does with the Linux kernel on ARM, I thought
> I better asked in the first place. :-)
> 
>> Please group all those patches in a patchset to avoid too much loose stuff on the list.
> 
> Point taken.
> 
> Thanks, and best regards,
> Peter Müller
> 
>> 
>> -Michael
>> 
>>> On 21 May 2021, at 10:18, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>> 
>>> Hello Arne,
>>> hello development folks (CC'ed),
>>> 
>>> the other day, I came across these two ARM-related kernel patches in ~/src/patches/, and am unsure
>>> if you still need them.
>>> 
>>> Could you please drop me a line if you don't, so I can delete them as well? :-)
>>> 
>>> Thanks, and best regards,
>>> Peter Müller
>> 


      reply	other threads:[~2021-05-21  9:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21  9:18 Peter Müller
2021-05-21  9:19 ` Michael Tremer
2021-05-21  9:24   ` Peter Müller
2021-05-21  9:25     ` Michael Tremer [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=100F2D11-0233-45AE-81A5-CB2F038B4D54@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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