From: Javier Martinez Canillas <martinez.javier@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Russell King <linux@arm.linux.org.uk>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Kevin Hilman <khilman@ti.com>,
"Govindraj.R" <govindraj.raja@ti.com>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/1] ARM: OMAP2+: enable devtmpfs and devtmpfs automount
Date: Fri, 14 Dec 2012 19:16:31 +0100 [thread overview]
Message-ID: <CAAwP0s1d4xPfYyaU+Cu=fH6YL5gmyYF+6x0aHOmNVeHshZ1ZeA@mail.gmail.com> (raw)
In-Reply-To: <20121214181051.GY4989@atomide.com>
On Fri, Dec 14, 2012 at 7:10 PM, Tony Lindgren <tony@atomide.com> wrote:
> * Javier Martinez Canillas <javier.martinez@collabora.co.uk> [121121 05:29]:
>> Since udev-182, udev no longer creates device nodes under /dev
>> and this has to be managed by the kernel devtmpfs filesystem.
>>
>> This means that a kernel built with the current OMAP2+ config
>> will not boot on a system with a recent udev.
>>
>> Also, it is good to have /dev automatically mounted since some
>> non-initramfs based setups assumes this and don't manually mount it.
>
> Thanks applying into omap-for-v3.8/fixes-for-merge-window.
>
> Regards,
>
> Tony
>
Hi Tony,
I resend a v2 today: [PATCH v2 1/1] ARM: OMAP2+: omap2plus_defconfig:
enable devtmpfs and automount
That fixes an issue in the patch comments. Sekar Nori pointed out that
the first udev to make this a requirement was 176 not 182.
So probably is better if you can apply that one instead.
Thanks a lot and best regards,
Javier
prev parent reply other threads:[~2012-12-14 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 13:26 [PATCH 1/1] ARM: OMAP2+: enable devtmpfs and devtmpfs automount Javier Martinez Canillas
2012-11-27 8:34 ` Sekhar Nori
2012-11-27 9:20 ` Javier Martinez Canillas
2012-12-14 18:10 ` Tony Lindgren
2012-12-14 18:16 ` Javier Martinez Canillas [this message]
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='CAAwP0s1d4xPfYyaU+Cu=fH6YL5gmyYF+6x0aHOmNVeHshZ1ZeA@mail.gmail.com' \
--to=martinez.javier@gmail.com \
--cc=govindraj.raja@ti.com \
--cc=javier.martinez@collabora.co.uk \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.com \
/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).