linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Apr 9
Date: Tue, 9 Apr 2013 16:11:50 +0200	[thread overview]
Message-ID: <CA+icZUVk-iLtodZi_46qmk410Ei+tW6RR5kV2fx0N8v6neKTPQ@mail.gmail.com> (raw)
In-Reply-To: <20130409235941.11eef57a42cb97efec72f037@canb.auug.org.au>

On Tue, Apr 9, 2013 at 3:59 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Sedat,
>
> On Tue, 9 Apr 2013 12:56:46 +0200 Sedat Dilek <sedat.dilek@gmail.com> wrote:
>>
>> This version hangs... I started in rescue-mode and see that udev,
>> premount and init scripts are run.
>> Currently, I have no glue why when what...
>> Lemme see if I get k(g)bd started.
>>
>> Unfortunately, there was a "quiet" boot-param for grub2 here but it's gone.
>> With "text" I don't see more.
>>
>> Maybe, someone has a hint.
>
> This is probably the known problem that Al Viro is looking at.  See "Boot
> hang due to "pipe: fold file_operations instances in one" in
> next-20130408" and  "Re: hangs on boot in 9984d7394618df9" thread on lkml
> and linux-next mailing lists.
>

[ CC Al Viro ]

Is there a "magic" git-command to revert all commits coming from your
latest vfs-merge (commit c1c04d3667608a630ae0821995b465a523e83fb1)?

2013-04-09 11:36 Stephen Rothwell   │ M─┐ │ │ │ │ │ │         │ 20130405/vfs

After reverting all these commits I would like to pull-in latest
vfs.git#for-next.

Thanks in advance.

- Sedat -

[1] http://git.kernel.org/cgit/linux/kernel/git/viro/vfs.git/log/?h=for-next

> --
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au

  parent reply	other threads:[~2013-04-09 14:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 10:56 linux-next: Tree for Apr 9 Sedat Dilek
2013-04-09 12:37 ` Sedat Dilek
2013-04-09 13:34   ` Sedat Dilek
2013-04-09 13:59 ` Stephen Rothwell
2013-04-09 14:03   ` Sedat Dilek
2013-04-09 14:11   ` Sedat Dilek [this message]
2013-04-09 14:23     ` Stephen Rothwell
2013-04-09 14:32       ` Sedat Dilek
2013-04-09 15:11         ` Sedat Dilek
2013-04-09 15:48           ` Sedat Dilek
  -- strict thread matches above, loose matches on Subject: below --
2024-04-09  4:50 Stephen Rothwell
2021-04-09 11:51 Stephen Rothwell
2020-04-09  5:10 Stephen Rothwell
2019-04-09  8:00 Stephen Rothwell
2019-04-09 18:25 ` Guenter Roeck
2019-04-09 18:44   ` Trond Myklebust
2018-04-09  4:42 Stephen Rothwell
2015-04-09  9:31 Stephen Rothwell
2014-04-09  7:22 Stephen Rothwell
2013-04-09  9:30 Stephen Rothwell

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=CA+icZUVk-iLtodZi_46qmk410Ei+tW6RR5kV2fx0N8v6neKTPQ@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).