All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Determining patch impact on a specific config
Date: Wed, 17 Aug 2016 15:52:16 +0200	[thread overview]
Message-ID: <20160817135216.GA1401@kroah.com> (raw)
In-Reply-To: <20160817132544.GA320@kroah.com>

On Wed, Aug 17, 2016 at 03:25:44PM +0200, Greg KH wrote:
> On Wed, Aug 17, 2016 at 12:39:39PM +0000, Nicholas Mc Guire wrote:
> > 
> > Hi !
> > 
> >  For a given patch I would like to find out if it impacts a
> >  given configuration or not. Now of course one could compile the
> >  kernel for the configuration prior to the patch, then apply the
> >  patch and recompile to find out if there is an impact but I would
> >  be looking for some smarter solution. Checking files only 
> >  unfortunately will not do it, due to ifdefs and friends so make
> >  would detect a change and recompile even if the affeted code 
> >  area is actualy dropped by the preprocessor.
> > 
> >  What Im trying to do is find out is, how many of the e.g. stable
> >  fixes of 4.4-4.4.14 would have impacted a given configuration - the
> >  whole exercise is intended for some statistical analysis of bugs
> >  in linux-stable.

Also, are you going to be analyizing the bugs in the stable trees, or
the ones we just happen to fix?

Note, that's not always the same thing :)

thanks,

greg k-h

  reply	other threads:[~2016-08-17 13:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17 12:39 Determining patch impact on a specific config Nicholas Mc Guire
2016-08-17 13:25 ` Greg KH
2016-08-17 13:52   ` Greg KH [this message]
2016-08-17 14:01     ` Nicholas Mc Guire
2016-08-17 14:17       ` Greg KH
2016-08-17 14:49         ` Nicholas Mc Guire
2016-08-17 15:39           ` Greg KH
2016-08-17 16:50             ` Nicholas Mc Guire
2016-08-17 17:34               ` Greg KH
2016-08-17 18:48                 ` Nicholas Mc Guire
2016-08-18  7:35                   ` Greg KH
2016-08-18  7:38                   ` Greg KH

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=20160817135216.GA1401@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.