mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Erkki Lintunen <ebirdie@iki.fi>
Cc: rdunlap@xenotime.net, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: bugfix for scripts/patch-kernel in 2.6 sublevel stepping
Date: Sun, 3 Aug 2008 15:00:19 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0808031458180.20768@shark.he.net> (raw)
In-Reply-To: <48961C6E.50000@iki.fi>

On Mon, 4 Aug 2008, Erkki Lintunen wrote:

> scripts/patch-kernel script can't patch a tree, say, from 2.6.25 to 2.6.26.1,
> because of a wrong comparison in context of patching 2.6.x base. Following
> patch has a fix for it.
> 
> Erkki

Hi,

This does work better than the current script in the kernel tree.

The larger question:  is does anyone still use this script?

Acked-by: Randy Dunlap <randy.dunlap@oracle.com>


Andrew, please merge.


> --- linux-2.6.26/scripts/patch-kernel   2008-04-27 19:49:14.000000000 +0300
> +++ linux-2.6.26.1/scripts/patch-kernel 2008-08-03 23:34:00.000000000 +0300
> @@ -213,6 +213,7 @@
>  if [ $stopvers != "default" ]; then
>         STOPSUBLEVEL=`echo $stopvers | cut -d. -f3`
>         STOPEXTRA=`echo $stopvers | cut -d. -f4`
> +       STOPFULLVERSION=${stopvers%%.$STOPEXTRA}
>         #echo "#___STOPSUBLEVEL=/$STOPSUBLEVEL/, STOPEXTRA=/$STOPEXTRA/"
>  else
>         STOPSUBLEVEL=9999
> @@ -249,7 +250,7 @@
>  do
>      CURRENTFULLVERSION="$VERSION.$PATCHLEVEL.$SUBLEVEL"
>      EXTRAVER=
> -    if [ $stopvers = $CURRENTFULLVERSION ]; then
> +    if [ $STOPFULLVERSION = $CURRENTFULLVERSION ]; then
>          echo "Stopping at $CURRENTFULLVERSION base as requested."
>          break
>      fi

-- 
~Randy

      reply	other threads:[~2008-08-03 22:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03 21:00 Erkki Lintunen
2008-08-03 22:00 ` Randy.Dunlap [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=Pine.LNX.4.64.0808031458180.20768@shark.he.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@linux-foundation.org \
    --cc=ebirdie@iki.fi \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®