On 8/4/14, 21:33, Kamble, Nitin A nitin.a.kam...@intel.com wrote:
On 8/4/2014 9:38 AM, Hart, Darren wrote:
On 7/29/14, 11:34, Kamble, Nitin A nitin.a.kam...@intel.com wrote:
...
+ if [ -n ${INITRD} ]; then
+ rm -f $dest/initrd
+ for fs in ${INITRD}
+ do
+
On 8/5/2014 9:45 AM, Hart, Darren wrote:
On 8/4/14, 21:33, Kamble, Nitin A nitin.a.kam...@intel.com wrote:
On 8/4/2014 9:38 AM, Hart, Darren wrote:
On 7/29/14, 11:34, Kamble, Nitin A nitin.a.kam...@intel.com wrote:
...
+ if [ -n ${INITRD} ]; then
+ rm -f $dest/initrd
+
On 7/29/14, 11:34, Kamble, Nitin A nitin.a.kam...@intel.com wrote:
From: Nitin A Kamble nitin.a.kam...@intel.com
Hi Nitin,
Generally speaking this looks like a good improvement. I don't have any
major technical concerns, but we do need to address some grammatical
issues in the commit and the
On 8/4/2014 9:38 AM, Hart, Darren wrote:
On 7/29/14, 11:34, Kamble, Nitin A nitin.a.kam...@intel.com wrote:
From: Nitin A Kamble nitin.a.kam...@intel.com
Hi Nitin,
Generally speaking this looks like a good improvement. I don't have any
major technical concerns, but we do need to address
From: Nitin A Kamble nitin.a.kam...@intel.com
The initrd image used by the Linux kernel is list of file system images
concatenated together and presented as a single initrd file at boot time.
So far the initrd is a single filesystem image. But in cases like to support
early microcode loading,
