Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1619002
| From | Thierry Reding <thierry.reding@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/1] memory: tegra: fix fdc test bug |
| Date | 2017-04-07 19:50 +0200 |
| Message-ID | <ttGbg-21h-9@gated-at.bofh.it> (permalink) |
| References | <ttGbg-21h-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Fri, Apr 07, 2017 at 06:28:20PM +0100, Ben Dooks wrote: > The fdc variable is a bool, taking the address of this will generally > produce true, thus skewing any users of the tegra_mc_set_latency_allowance > code. > > Note, this does not seem to be producing a compiler warning. This was only > spotted as it meant a caller was seeing 3 times higher than expected > register results. > > Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk> > --- > drivers/memory/tegra/mc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) What tree is this based on? I don't see this code anywhere in mainline. Thierry
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCH 1/1] memory: tegra: fix fdc test bug Thierry Reding <thierry.reding@gmail.com> - 2017-04-07 19:50 +0200 Re: [PATCH 1/1] memory: tegra: fix fdc test bug Ben Dooks <ben.dooks@codethink.co.uk> - 2017-04-08 00:00 +0200
csiph-web