From: "David Fernández" <david@dit.upm.es>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] ubd option parsing problem when using cow filesystems in kernel 3.4
Date: Thu, 21 Jun 2012 16:29:18 +0200 [thread overview]
Message-ID: <4FE32FBE.4050201@dit.upm.es> (raw)
In-Reply-To: <CAFLxGvw4=mcfqd_0HbP17AR5ZqR-NqMSVgPgFyYamTSu=vgfOQ@mail.gmail.com>
On 20/06/12 19:13, richard -rw- weinberger wrote:
> On Wed, Jun 20, 2012 at 7:02 PM, David Fernández<david@dit.upm.es> wrote:
>> Finally I managed to do the git bisect with your indications. The result:
>>
>> # git bisect bad
>> 026cee0086fe1df4cf74691cf273062cc769617d is the first bad commit
>> commit 026cee0086fe1df4cf74691cf273062cc769617d
>> Author: Pawel Moll<pawel.moll@arm.com>
>> Date: Mon Mar 26 12:50:51 2012 +1030
>>
>> params:<level>_initcall-like kernel parameters
>>
>> This patch adds a set of macros that can be used to declare
>> kernel parameters to be parsed _before_ initcalls at a chosen
>> level are executed. We rename the now-unused "flags" field of
>> struct kernel_param as the level. It's signed, for when we
>> use this for early params as well, in future.
>>
>> Linker macro collating init calls had to be modified in order
>> to add additional symbols between levels that are later used
>> by the init code to split the calls into blocks.
>>
>> Signed-off-by: Pawel Moll<pawel.moll@arm.com>
>> Signed-off-by: Rusty Russell<rusty@rustcorp.com.au>
> Interesting.
> Reverting this commit makes the problem go away?
What command should I use to revert that specific commit? I'm not an
expert in git, in fact I just learnt what a 'git bisect' is after your
message ...:-)
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2012-06-21 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 8:55 [uml-devel] ubd option parsing problem when using cow filesystems in kernel 3.4 David Fernández
2012-06-19 9:03 ` richard -rw- weinberger
2012-06-19 22:33 ` David Fernández
2012-06-20 7:17 ` richard -rw- weinberger
2012-06-20 17:02 ` David Fernández
2012-06-20 17:13 ` richard -rw- weinberger
2012-06-21 14:29 ` David Fernández [this message]
2012-06-21 14:42 ` richard -rw- weinberger
2012-06-21 14:49 ` Geert Uytterhoeven
2012-06-25 0:30 ` David Fernández
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=4FE32FBE.4050201@dit.upm.es \
--to=david@dit.upm.es \
--cc=richard.weinberger@gmail.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.