public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Thorsten Glaser <tg@mirbsd.de>
Cc: Debian Kernel Team <debian-kernel@lists.debian.org>,
	linux-m68k@vger.kernel.org
Subject: Re: Debian/m68k kernel (preview)
Date: Sun, 24 Apr 2011 05:00:02 +0100	[thread overview]
Message-ID: <1303617602.3032.86.camel@localhost> (raw)
In-Reply-To: <Pine.BSM.4.64L.1104232054070.3979@herc.mirbsd.org>

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

On Sat, 2011-04-23 at 21:00 +0000, Thorsten Glaser wrote:
> Christian T. Steigies dixit:
> 
> >As Geert wrote, almost all patches will make it into the official kernel
> >tree, only m68k usually needs them a little sooner.
> 
> OK, I’ve tracked down the patches that were indeed submitted,
> added the SLUB workaround, and prepared another source package.
> It’s currently building (cross, for speed of testing), but if
> you like, you can review the patch I’d ask the Debian Kernel
> Team to include later (if this works). My patch is based on
> linux-2.6_2.6.38-3 since that’s what was in main when I began,
> but should work against the scheduled -4, too. I’ve reduced
> the number of patches to what I think is the minimum needed.

You don't need to unset ECONET or X25 in debian/config/m68k/config; they
are explicitly unset in the top-level config.

> Some of the changes to debian/config/m68k/* were already in
> sid/2.6.32 in Debian but not in what was trunk back then, so
> I’ve re-added them. I think they come from Stephen Marenka.
> 
> I don’t know how the ABI files are generated, there’s none for
> m68k yet. Please tell me if I have to do something.
[...]

They are based on the Module.symvers files generated during a build and
included in the linux-headers-* packages.  They are added to the *next*
version of the source package if we are intending to maintain the ABI,
using debian/bin/abiupdate.py.  If there has not been a successful build
of kernel version '2.6.38-2' for m68k then there is no need to add them.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2011-04-24  4:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21  8:19 Fix for SLUB? (was: Fwd: [PATCH v3] mm: make expand_downwards symmetrical to expand_upwards) Geert Uytterhoeven
2011-04-23  1:31 ` Michael Schmitz
2011-04-23  2:14   ` Michael Schmitz
2011-04-23  3:47     ` Michael Schmitz
2011-04-23 13:08       ` Geert Uytterhoeven
2011-04-23 15:39         ` Fix for SLUB? Thorsten Glaser
2011-04-23 18:57           ` Christian T. Steigies
2011-04-23 21:00             ` Debian/m68k kernel (preview) Thorsten Glaser
2011-04-24  4:00               ` Ben Hutchings [this message]
2011-04-24 11:18                 ` Thorsten Glaser
2011-04-24 20:07                 ` Thorsten Glaser
2011-04-25  3:08                   ` Michael Schmitz
2011-04-24  2:06             ` Fix for SLUB? Michael Schmitz
2011-04-24  8:26               ` Geert Uytterhoeven
2011-04-23 17:09       ` Fix for SLUB? (was: Fwd: [PATCH v3] mm: make expand_downwards symmetrical to expand_upwards) Andreas Schwab
2011-04-24  2:19         ` Michael Schmitz

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=1303617602.3032.86.camel@localhost \
    --to=ben@decadent.org.uk \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=tg@mirbsd.de \
    /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