public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Petru Paler <ppetru@ppetru.net>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sparc64 compile fix
Date: Sun, 14 Jan 2001 01:01:25 +0200	[thread overview]
Message-ID: <20010114010125.M2734@ppetru.net> (raw)
In-Reply-To: <20010113152104.B2734@ppetru.net> <14944.56558.198555.536993@pizda.ninka.net>
In-Reply-To: <14944.56558.198555.536993@pizda.ninka.net>; from davem@redhat.com on Sat, Jan 13, 2001 at 02:55:42PM -0800

On Sat, Jan 13, 2001 at 02:55:42PM -0800, David S. Miller wrote:
> Petru Paler writes:
>  > -       struct dqblk d;
>  > +       struct dqblk32 d;
> 
> What does this fix?  Things compile just fine without
> it and looking at the code it was intended to be of
> the original type.
> 
> Please explain exactly what submitted patches fix in
> the future, thanks.

Sorry, my fingers slipped and I sent the mail too fast :(

Trying to compile 2.4.0-ac8 resulted in an error about
storage size of variable d not being known (I don't have the
exact error at hand, the network connectivity to that server
is down right now). Changing it to dqblk32 got it to compile.

Am I doing something else wrong ?

--
Petru Paler, mailto:ppetru@ppetru.net
http://www.ppetru.net - ICQ: 41817235
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-13 23:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-13 13:21 [PATCH] sparc64 compile fix Petru Paler
2001-01-13 22:55 ` David S. Miller
2001-01-13 23:01   ` Petru Paler [this message]
2001-01-14  9:19     ` David S. Miller
2001-01-14  9:32       ` Petru Paler
2001-01-13 23:15   ` Alan Cox

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=20010114010125.M2734@ppetru.net \
    --to=ppetru@ppetru.net \
    --cc=davem@redhat.com \
    --cc=linux-kernel@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