All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
To: yocto@yoctoproject.org
Subject: modify a kernel patch
Date: Mon, 7 May 2012 16:41:08 +0200	[thread overview]
Message-ID: <CACW_hTacgFqj2NQZ4aNuN5WBm2R9Ge3NS25XVJTKjmKm6spHKw@mail.gmail.com> (raw)

Hi all,

Not sure what the best place is to mail this (the YP list or oe-core
or oe-devel or ...)
Apologies if this is the wrong place.

The problem I'm facing is the following:
I have a kernel with some additional drivers that are not upstreamed
because they are very specifc.
I'm moving from oe-classic to denzil and from 2.6.38 to 3.2.
Now some of the patches do not apply any more.
In oe-classic I would have gone to the kernel work dir, fix the issue,
do a quilt refresh and copy the patch back (there is a patch that
contains our driver)
However, denzil uses guilt instead of quilt

If I do a devshell of virtual/kernel and want to do with guilt what I
used to do with quilt I run into a problem.
guilt status says: Patches directory does not exist, try guilt-init
and indeed there is no patches dir like there was in oe-classic

Hence my question:
What is a good workflow to modify a kernel patch.
Or, what magic incantation do I need to give to guilt to make it working.

Any suggestion is greatly appreciated.

Have fun!
Frans.


             reply	other threads:[~2012-05-07 14:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 14:41 Frans Meulenbroeks [this message]
2012-05-07 14:48 ` modify a kernel patch Bruce Ashfield
2012-05-07 19:29   ` Frans Meulenbroeks
2012-05-07 19:36     ` Bruce Ashfield
2012-05-08  7:18       ` Frans Meulenbroeks
2012-05-08 12:42         ` Bruce Ashfield
2012-05-08 13:03           ` Frans Meulenbroeks
2012-05-08 13:22             ` Bruce Ashfield
2012-05-08 19:20             ` Bruce Ashfield
2012-05-08 22:40               ` Autif Khan
2012-05-09  1:12                 ` Bruce Ashfield
2012-05-09  4:31                   ` Khem Raj
2012-05-09 14:11               ` Frans Meulenbroeks
2012-05-09 14:14                 ` Bruce Ashfield
2012-05-09 14:27                   ` Frans Meulenbroeks
2012-05-09 14:40                     ` Bruce Ashfield

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=CACW_hTacgFqj2NQZ4aNuN5WBm2R9Ge3NS25XVJTKjmKm6spHKw@mail.gmail.com \
    --to=fransmeulenbroeks@gmail.com \
    --cc=yocto@yoctoproject.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.