From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 121891] Canadian Call's $@$@$@$@**@185587O92847+@***++ 7 ++++ E.p.s.o.n. p.r.i.n.t.e.r c.u.s.t.o.m.e.r S.u.p.p.o.rt p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l.pdf
Date: Sun, 29 May 2022 11:14:51 +0000 [thread overview]
Message-ID: <bug-121891-11311-yXK3cTWWl9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-121891-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=121891
kaleabernathy@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kaleabernathy@gmail.com
--- Comment #1 from kaleabernathy@gmail.com ---
There is an evident copy and paste problem in the files gpmc.c (version 3.14)
and omap-gpmc.c, as noted in the summary (version 4.6).
The versions between these haven't been examined, although the problem is very
certainly there.
GPMC_CONFIG4_WEEXTRADELAY is a constant that is declared but never utilized.
GPMC_CONFIG4_OEEXTRADELAY is used instead where it should be.
In version 3.14, the incorrect line is located at
arch/arm/mach-omap2/gpmc.c:275.
The incorrect line is located in drivers/memory/omap-gpmc.c:379 in 4.6
https://cupcake-2048.com
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2022-05-29 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 16:33 [Bug 121891] New: Canadian Call's $@$@$@$@**@185587O92847+@***++ 7 ++++ E.p.s.o.n. p.r.i.n.t.e.r c.u.s.t.o.m.e.r S.u.p.p.o.rt p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l.pdf bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
[not found] ` <bug-121891-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2016-07-12 11:26 ` [Bug 121891] " bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2022-05-29 11:14 ` bugzilla-daemon [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=bug-121891-11311-yXK3cTWWl9@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.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