From: Greg KH <gregkh@linuxfoundation.org>
To: B_B_Singh@DELL.com
Cc: tiwai@suse.de, Abhay_Salunke@DELL.com, arnd@arndb.de,
kay@vrfy.org, ming.lei@canonical.com, sr@denx.de, teg@jklm.no,
Stuart_Hayes@DELL.com, Srinivas_G_Gowda@DELL.com,
linux-kernel@vger.kernel.org
Subject: Re: patch "firmware loader: allow disabling of udev as firmware loader" added to driver-core tree
Date: Thu, 10 Jul 2014 07:54:17 -0700 [thread overview]
Message-ID: <20140710145417.GB18412@kroah.com> (raw)
In-Reply-To: <8B2F6FFD0BD1E448853114367400A37306FD6FBBF0@BLRX7MCDC203.AMER.DELL.COM>
On Thu, Jul 10, 2014 at 08:10:01PM +0530, B_B_Singh@DELL.com wrote:
> Resending the mail..
>
> Hi All,
>
> As I communicated earlier the test never passed with older BIOS DUPs.
That test? What patch? Please be explicit, I deal with thousands of
patches and have no short term memory...
> Again today I have tested with 3.15.5 kernel with below patch applied,
> & I don't see the BIOS getting updated. The BIOS update always failed
> with below patch.
>
> I'm not sure why the patch is getting committed even upon failure.
Because in that long and winding email thread I thought you said this
patch _worked_. Obviously I was wrong, sorry, please suggest an
alternative.
greg k-h
next parent reply other threads:[~2014-07-10 14:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14048583172593@kroah.com>
[not found] ` <8B2F6FFD0BD1E448853114367400A37306FD6FBBE9@BLRX7MCDC203.AMER.DELL.COM>
[not found] ` <20140710143144.GA17639@kroah.com>
[not found] ` <8B2F6FFD0BD1E448853114367400A37306FD6FBBF0@BLRX7MCDC203.AMER.DELL.COM>
2014-07-10 14:54 ` Greg KH [this message]
2014-07-10 15:24 ` B_B_Singh
[not found] ` <s5h38e9mg5v.wl%tiwai@suse.de>
[not found] ` <8B2F6FFD0BD1E448853114367400A37306FD6FBBF8@BLRX7MCDC203.AMER.DELL.COM>
[not found] ` <s5hy4w1l0s3.wl%tiwai@suse.de>
[not found] ` <8B2F6FFD0BD1E448853114367400A37306FD6FBC06@BLRX7MCDC203.AMER.DELL.COM>
[not found] ` <s5hpphdkyi6.wl%tiwai@suse.de>
[not found] ` <8B2F6FFD0BD1E448853114367400A37306FD6FBDAB@BLRX7MCDC203.AMER.DELL.COM>
[not found] ` <s5hoawvkimg.wl%tiwai@suse.de>
[not found] ` <8B2F6FFD0BD1E448853114367400A37306FE07C773@BLRX7MCDC203.AMER.DELL.COM>
[not found] ` <s5h7g3frmg7.wl%tiwai@suse.de>
[not found] ` <8B2F6FFD0BD1E448853114367400A37306FE07CC64@BLRX7MCDC203.AMER.DELL.COM>
[not found] ` <s5hlhrrizbq.wl%tiwai@suse.de>
2014-08-01 20:01 ` B_B_Singh
2014-08-05 15:43 ` Jean-Michel Hautbois
2014-08-05 15:53 ` Takashi Iwai
2014-08-05 15:55 ` Jean-Michel Hautbois
2014-08-05 16:01 ` Takashi Iwai
2014-08-05 19:22 ` Shuah Khan
2014-08-06 9:10 ` Jean-Michel Hautbois
2014-08-06 9:24 ` Takashi Iwai
2014-08-06 9:44 ` Jean-Michel Hautbois
2014-08-06 10:21 ` Takashi Iwai
2014-08-06 10:50 ` Jean-Michel Hautbois
2014-08-06 10:52 ` Takashi Iwai
2014-08-06 11:24 ` Jean-Michel Hautbois
2014-08-06 12:24 ` Takashi Iwai
2014-08-06 19:00 ` Shuah Khan
2014-08-07 7:57 ` Takashi Iwai
2014-08-07 13:23 ` Shuah Khan
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=20140710145417.GB18412@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Abhay_Salunke@DELL.com \
--cc=B_B_Singh@DELL.com \
--cc=Srinivas_G_Gowda@DELL.com \
--cc=Stuart_Hayes@DELL.com \
--cc=arnd@arndb.de \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=sr@denx.de \
--cc=teg@jklm.no \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®