From: Torbjorn Granlund <tege@pdc.kth.se>
To: "David S. Miller" <davem@jenolan.rutgers.edu>
Cc: egcs@cygnus.com
Subject: Re: This was fun to track down
Date: Tue, 23 Sep 1997 13:41:00 -0000 [thread overview]
Message-ID: <199709232041.WAA03487@squid.pdc.kth.se> (raw)
In-Reply-To: <199709230236.WAA13146@jenolan.rutgers.edu>
That change is wrong. It is not the right way to fix the observed problem.
Jeff, I think you should take it out again.
I asked for a trigger case, since being the person who wrote expand_divmod,
it makes sense that I fix problems in it. But I got no test case.
Torbjorn
next prev parent reply other threads:[~1997-09-23 13:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-22 19:37 David S. Miller
1997-09-23 0:25 ` Jeffrey A Law
1997-09-23 1:49 ` Torbjorn Granlund
1997-09-23 14:09 ` David S. Miller
1997-09-23 13:41 ` Torbjorn Granlund [this message]
1997-09-23 13:50 ` David S. Miller
1997-09-23 13:57 ` Torbjorn Granlund
1997-09-23 14:16 ` David S. Miller
1997-09-23 19:05 ` Jeffrey A Law
1997-09-24 12:58 ` Jim Wilson
1997-09-24 23:15 ` Jeffrey A Law
1997-09-27 13:40 ` Torbjorn Granlund
1997-09-27 23:38 ` Jeffrey A Law
1997-09-29 11:53 ` Jim Wilson
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=199709232041.WAA03487@squid.pdc.kth.se \
--to=tege@pdc.kth.se \
--cc=davem@jenolan.rutgers.edu \
--cc=egcs@cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).