All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: "François Valenduc" <francoisvalenduc@gmail.com>, stable@vger.kernel.org
Subject: Re: Linux 4.14.10
Date: Tue, 16 Jan 2018 06:54:37 +0100	[thread overview]
Message-ID: <20180116055437.GD18698@kroah.com> (raw)
In-Reply-To: <21b9c8c7-3c61-5762-85f1-f46affde4c0a@applied-asynchrony.com>

On Mon, Jan 15, 2018 at 11:07:33PM +0100, Holger Hoffst�tte wrote:
> On 12/29/17 18:42, Greg KH wrote:
> > On Fri, Dec 29, 2017 at 06:38:15PM +0100, Fran�ois Valenduc wrote:
> >> Le 29/12/17 � 18:32, Greg KH a �crit�:
> >>> On Fri, Dec 29, 2017 at 06:18:18PM +0100, Fran�ois Valenduc wrote:
> >>>> No solution found to the permissions on tools/objtool/sync-check.sh  ?
> >>> Is the permission not correct in the repo?  Is it not correct in the
> >>> patch I sent out in response to this?
> >>>
> >>>> git or patch is not smart enough for that ? It's obviously extremely
> >>>> easy to solve the problem, but I find that rather strange.
> >>> git and patch handle it just fine, quilt has issues, which I worked
> >>> around very easily.  Are you having problems with the git tree as-is?
> >>>
> >>> thanks,
> >>>
> >>> greg k-h
> >>
> >> It seems I messed up with enigmail. So in case you couldn't read my
> >> reply, I send it again.
> >>
> >> I didn't see the posts of Toralf Forster before replying to your
> >> annoucement. But my problem is exactly the same. I extracted the patch
> >> from git (with git diff v4.14.9..v4.14.10). The permissions are also
> >> wrong if I download the patch from kernel.org. In both cases,
> >> sync-check.sh is not executable.
> > 
> > That's fine, but when you apply the patch, you need to keep the file
> > mode.  So be careful as to how you apply it.
> > 
> > I just got told that there's a patch in Andrew's tree that fixes this
> > (it doesn't rely on the mode of the file.)  Hopefully it gets into
> > Linus's tree soon and then I can queue it up into the stable tree to
> > help people who don't only use git.
> 
> This is now in 4.15-rc8 as commit 0f908ccbeca aka:
> "tools/objtool/Makefile: don't assume sync-check.sh is executable"
> 
> I've been using it since it came out, would be great to add that
> to all stable series where 3bd51c5a371de was applied.

Thanks, I'll queue it up for the next round after this one.  Then the
gentoo users will be a bit happier :)

greg k-h

      reply	other threads:[~2018-01-16  5:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 17:10 Linux 4.14.10 Greg KH
2017-12-29 17:11 ` Greg KH
2017-12-29 17:18 ` François Valenduc
2017-12-29 17:32   ` Greg KH
2017-12-29 17:38     ` François Valenduc
2017-12-29 17:42       ` Greg KH
2017-12-30 15:48         ` François Valenduc
2017-12-30 15:54           ` Greg KH
2018-01-15 22:07         ` Holger Hoffstätte
2018-01-16  5:54           ` Greg KH [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=20180116055437.GD18698@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=francoisvalenduc@gmail.com \
    --cc=holger@applied-asynchrony.com \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.