From: Dmitry Torokhov <dtor@vmware.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: boot problen with next-20110211
Date: Thu, 10 Feb 2011 23:06:42 -0800 [thread overview]
Message-ID: <20110211070642.GA9512@dtor-ws.eng.vmware.com> (raw)
In-Reply-To: <20110211065731.GA8861@dtor-ws.eng.vmware.com>
On Thu, Feb 10, 2011 at 10:57:31PM -0800, Dmitry Torokhov wrote:
> Hi Stephen,
>
> On Thu, Feb 10, 2011 at 10:22:54PM -0800, Stephen Rothwell wrote:
> >
> > Maybe the module parameter alignment patches? That is a very strange
> > parameter name (it is the same in the other messages).
>
> Yes, I think it is... I wonder why I did not see it locally. Let me try
> to fix that...
>
Gah, it is better Rusty drops the module param alignment patch so I can
redo it properly. The module case is completely broken as it still
operates with assumption that __param section contains full structures
and not pointers.
--
Dmitry
next prev parent reply other threads:[~2011-02-11 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 6:22 linux-next: boot problen with next-20110211 Stephen Rothwell
2011-02-11 6:57 ` Dmitry Torokhov
2011-02-11 7:06 ` Dmitry Torokhov [this message]
2011-02-11 8:37 ` Dmitry Torokhov
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=20110211070642.GA9512@dtor-ws.eng.vmware.com \
--to=dtor@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 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.