From: maximilian attems <max@stro.at>
To: Thorsten Glaser <tg@mirbsd.de>
Cc: Debian Kernel Team <debian-kernel@lists.debian.org>,
linux-m68k@vger.kernel.org
Subject: Re: [m68k] Patches for 3.0 (was Re: linux-2.6_2.6.39-1_amd64.changes ACCEPTED into unstable)
Date: Wed, 29 Jun 2011 21:53:16 +0000 [thread overview]
Message-ID: <20110629215316.GA1072@vostochny.stro.at> (raw)
In-Reply-To: <Pine.BSM.4.64L.1106292002530.32507@herc.mirbsd.org>
hello,
On Wed, Jun 29, 2011 at 08:05:11PM +0000, Thorsten Glaser wrote:
> Hi Debian Kernel team,
>
> can we please have these for 3.0? They will be in 3.1, and replace
> 0008-m68k-atari-Reserve-some-ST-RAM-early-on-for-device-b.patch
> from 2.6.38-2, addressing the same problem (garbled video output
> when the machine has too much FastRAM).
aboves confuses me, I don't see any m68k patches in the trunk branch
heading for the next 3.0-rcX upload?
which are needed?
> Thanks!
>
>
>
> Geert Uytterhoeven dixit:
>
> >On Wed, Jun 29, 2011 at 19:38, Thorsten Glaser <tg@mirbsd.de> wrote:
> >> Geert Uytterhoeven dixit:
> >>
> >>>I folded it into your previous patch and pushed it out for 3.1.
> >>
> >> Can you make a patch (series) on top of 3.0 and mail that to
> >> debian-kernel asking for inclusion in the next 3.0 upload, on
> >> the ground it’s been accepted upstream and fixes UI problems?
> >
> >The two patches you need are
> >
> >http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git;a=commitdiff;h=1789c38726c2805563e9049dbc5d5253251761a7
> >http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git;a=commitdiff;h=10b2495b79eb8c2b6ec92b3ce1e5577f892f7821
> >
> >which are both on my for-3.1/for-next branch:
> >
> >http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git;a=shortlog;h=refs/heads/for-3.1
> >
> >Gr{oetje,eeting}s,
> >
> > Geert
ah ok I see, will wait till these 2 materialise in linux-next and
then add them.
thanks.
--
maks
next prev parent reply other threads:[~2011-06-29 21:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1QNV5z-0006jD-Ej@franck.debian.org>
[not found] ` <20110521122605.GA16345@chumley.earth.sol>
[not found] ` <Pine.BSM.4.64L.1105211232060.14234@herc.mirbsd.org>
[not found] ` <Pine.BSM.4.64L.1105211327140.14234@herc.mirbsd.org>
2011-05-24 12:22 ` linux-2.6_2.6.39-1_amd64.changes ACCEPTED into unstable Geert Uytterhoeven
2011-05-30 17:14 ` Michael Schmitz
2011-05-30 17:22 ` Geert Uytterhoeven
2011-06-13 18:49 ` Geert Uytterhoeven
2011-06-13 20:35 ` Michael Schmitz
2011-06-19 4:30 ` Michael Schmitz
2011-06-19 7:37 ` Andreas Schwab
2011-06-19 20:08 ` Michael Schmitz
2011-06-26 23:49 ` Michael Schmitz
2011-06-27 6:56 ` Geert Uytterhoeven
2011-06-29 11:19 ` Geert Uytterhoeven
2011-06-29 17:38 ` Thorsten Glaser
2011-06-29 19:33 ` Geert Uytterhoeven
2011-06-29 20:05 ` [m68k] Patches for 3.0 (was Re: linux-2.6_2.6.39-1_amd64.changes ACCEPTED into unstable) Thorsten Glaser
2011-06-29 21:53 ` maximilian attems [this message]
2011-06-29 21:59 ` [m68k] Patches for 3.0 Thorsten Glaser
2011-07-03 18:18 ` maximilian attems
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=20110629215316.GA1072@vostochny.stro.at \
--to=max@stro.at \
--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