mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: David Miller <davem@davemloft.net>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] sparc: Provide cmpxchg64 for 32-bit builds
Date: Thu, 9 Nov 2017 07:53:23 -0800	[thread overview]
Message-ID: <20171109155323.GA19959@roeck-us.net> (raw)
In-Reply-To: <20171109.152852.88103578951782189.davem@davemloft.net>

On Thu, Nov 09, 2017 at 03:28:52PM +0900, David Miller wrote:
> From: Guenter Roeck <linux@roeck-us.net>
> Date: Mon,  6 Nov 2017 06:41:45 -0800
> 
> > Fix the following build error, seen when building sparc32:allmodconfig.
> > 
> > drivers/net/ethernet/intel/i40e/i40e_ethtool.c:
> > 	In function 'i40e_set_priv_flags':
> > drivers/net/ethernet/intel/i40e/i40e_ethtool.c:4150:2: error:
> > 	implicit declaration of function 'cmpxchg64'
> > 
> > Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> 
> Guenter, are you really not seeing this commit which has been
> in my sparc GIT tree for a while?
> 
Dave,

At least as of yesterday, the patch had not found its way into mainline.

I am running kernel build tests in my spare time, as community service.
I do spend time before I submit a report or a proposed patch trying to
find if the problem or its fix was already posted, just to avoid the
"you dummy, this was already fixed" type feedback. However, I typically
don't repeat that if it appears that the original report or submission
was ignored. I just don't have the time to do that.

So, no, I did not see the patch in your tree. Sorry for the noise.
I'll refrain from reporting problems on sparc to avoid such noise
in the future. I'll definitely no longer send out reminders.

Guenter

      reply	other threads:[~2017-11-09 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 14:41 Guenter Roeck
2017-11-09  6:28 ` David Miller
2017-11-09 15:53   ` Guenter Roeck [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=20171109155323.GA19959@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@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

all inboxes | Powered by JetHome®