From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: vexpress_defconfig: Allow to boot using a regular filesystem on SD card
Date: Wed, 21 Aug 2013 16:19:35 -0700	[thread overview]
Message-ID: <CAMJs5B9-u2ciE6B98rGXyO2fZKUtTn1AhDtYk5nMwu0DR_5P=g@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdbruw8J26cva-kgXXZuMM-8z9BFpuaY=_QJqCzYYdVaqw@mail.gmail.com>
On 21 August 2013 15:57, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Wed, Aug 21, 2013 at 12:51 PM, Pawel Moll <pawel.moll@arm.com> wrote:
>
>> This gets down to the question do we actually want the
>> vexpress_defconfig at all?
>
> I added it because people were complaining that I was not
> testing code against Vexpress and there was no way to
> conveniently do that without a defconfig.
>
> It is also used in Rothwells kisskb:
> http://kisskb.ellerman.id.au/kisskb/branch/9/
>
And it's mentioned in a wide variety of guides concerning building
QEMU/KVM guest images - I think it would be premature to remove it.
-Christoffer
     prev parent reply	other threads:[~2013-08-21 23:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 21:02 [PATCH 0/3] ARM: vexpress_defconfig: Allow to boot using a regular filesystem on SD card Fathi Boudra
2013-08-20 21:02 ` [PATCH 1/3] ARM: vexpress_defconfig: Enable and automount devtmpfs filesystem Fathi Boudra
2013-08-21 10:46   ` Pawel Moll
2013-08-21 19:11     ` Fathi Boudra
2013-08-20 21:02 ` [PATCH 2/3] ARM: vexpress_defconfig: Enable voltage regulator support Fathi Boudra
2013-08-21 10:48   ` Pawel Moll
2013-08-20 21:02 ` [PATCH 3/3] ARM: vexpress_defconfig: Enable ext4 filesystem Fathi Boudra
2013-08-21  9:05 ` [PATCH 0/3] ARM: vexpress_defconfig: Allow to boot using a regular filesystem on SD card Jon Medhurst (Tixy)
2013-08-21 10:51   ` Pawel Moll
2013-08-21 10:53     ` Russell King - ARM Linux
2013-08-21 22:57     ` Linus Walleij
2013-08-21 23:19       ` Christoffer Dall [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='CAMJs5B9-u2ciE6B98rGXyO2fZKUtTn1AhDtYk5nMwu0DR_5P=g@mail.gmail.com' \
    --to=christoffer.dall@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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 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).