public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] m68k/mac: Make SCC reset work more reliably
Date: Wed, 15 Jan 2014 08:15:41 +1100 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1401150731340.6166@nippy.intranet> (raw)
In-Reply-To: <CAMuHMdWuGPjyU_7fQKzgFsjm2w5wH38rSi_8ct7OiskZkrz+ng@mail.gmail.com>


On Tue, 14 Jan 2014, Geert Uytterhoeven wrote:

> 
> > I'm unsure about submitting this to -stable. I don't like the idea 
> > that the first debian user to boot a powerbook might see a crash 
> > (depending on bootloader etc). But not all stable trees carry df66834a 
> > which is a prerequisite. This patch is only applicable to 3.4.y and >= 
> > 3.9.y. Can you nominate particular stable trees?
> 
> Sure, just add it to the comment, cfr. 
> Documentation/stable_kernel_rules.txt:

Yes. I read the docs before I wrote.

> 
>  - If the patch requires other patches as prerequisites which can be 
>    cherry-picked than this can be specified in the following format in 
>    the sign-off area:
> 
>      Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
>      Cc: <stable@vger.kernel.org> # 3.3.x: 1b9508f: sched: Rate-limit newidle
>      Cc: <stable@vger.kernel.org> # 3.3.x: fd21073: sched: Fix affinity logic
>      Cc: <stable@vger.kernel.org> # 3.3.x

I didn't want the commit to be cherry-picked as it's already there (under 
different commit IDs) in some stable trees.

The prerequisite commit is df66834a in mainline (merged in 3.10). It is 
known as f64747c9 in 3.9.y and 8cfd67a3 in 3.4.y.

I only checked the trees in linux-stable.git which is not exhaustive but 
there are some stable trees that don't have it at all.

Perhaps it would be best to request that the new patch only gets applied 
where the prerequisite patch was already in mainline, i.e. >= 3.10.

Finn

> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 

  reply	other threads:[~2014-01-14 21:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12 13:56 [PATCH] m68k/mac: Make SCC reset work more reliably Finn Thain
2014-01-13 15:47 ` Geert Uytterhoeven
2014-01-14  8:31   ` Finn Thain
2014-01-14  8:52     ` Geert Uytterhoeven
2014-01-14 21:15       ` Finn Thain [this message]
2014-01-16 11:18         ` Thorsten Glaser
2014-01-19 10:56 ` Geert Uytterhoeven

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=alpine.LNX.2.00.1401150731340.6166@nippy.intranet \
    --to=fthain@telegraphics.com.au \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.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