From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Sampsa Ranta <sampsa@netsonic.fi>
Cc: <linux-kernel@vger.kernel.org>, laughing@shared-source.org
Subject: Re: Linux 2.4.7-ac9 (breaks ATM connect)
Date: Thu, 9 Aug 2001 21:32:32 MET-1 [thread overview]
Message-ID: <15F8646133@vcnet.vc.cvut.cz> (raw)
On 9 Aug 01 at 22:27, Sampsa Ranta wrote:
> On Thu, 9 Aug 2001, Sampsa Ranta wrote:
>
> > - vci != ATM_VCI_ANY && vci >> dev->ci_range.vci_bits))
> + vci != ATM_VCI_ANY && vci >= 1 << dev->ci_range.vci_bits))
As these two are equivalent, probably just reverting patch back
to '>>' is easiest... Maybe that second one is more readable, but
I do not think.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2001-08-09 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 21:32 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-07 22:53 Linux 2.4.7-ac9 Alan Cox
2001-08-09 19:24 ` Linux 2.4.7-ac9 (breaks ATM connect) Sampsa Ranta
2001-08-09 19:27 ` Sampsa Ranta
2001-08-09 20:30 ` David S. Miller
2001-08-09 20:52 ` Chris Friesen
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=15F8646133@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=laughing@shared-source.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sampsa@netsonic.fi \
/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