From: Samuel Ortiz <sameo@linux.intel.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kbuild test robot <lkp@intel.com>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.
Date: Wed, 29 Mar 2017 08:51:04 +0200 [thread overview]
Message-ID: <20170329065104.GB30988@zurbaran.ger.intel.com> (raw)
In-Reply-To: <CAP=VYLovck5PFD-5C93QahwkGv3ygkWaKjGy90MjNtEodF242Q@mail.gmail.com>
Hi Paul,
On Tue, Mar 28, 2017 at 06:55:26PM -0400, Paul Gortmaker wrote:
> On Mon, Jan 9, 2017 at 12:52 PM, Paul Gortmaker
> <paul.gortmaker@windriver.com> wrote:
> > Currently ia64 fails building allmodconfig with variations of:
> >
> > In file included from drivers/nfc/nxp-nci/i2c.c:39:0:
> > ./include/linux/unaligned/access_ok.h:62:29: error: redefinition of ‘put_unaligned_be64’
> > static __always_inline void put_unaligned_be64(u64 val, void *p)
>
> Hi Samuel,
>
> Do you require changes on this commit, or are you happy to queue it as is?
> Looking at the NFC git history it seems like you are the right person to ask.
I will queue it later this week, sorry for the lag.
Cheers,
Samuel.
next prev parent reply other threads:[~2017-03-29 6:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 0:19 [PATCH] nfc: don't be making arch specific unaligned decisions at driver level Paul Gortmaker
2017-01-09 0:47 ` kbuild test robot
2017-01-09 0:56 ` kbuild test robot
2017-01-09 17:52 ` [PATCH v2] " Paul Gortmaker
2017-03-28 22:55 ` Paul Gortmaker
2017-03-29 6:51 ` Samuel Ortiz [this message]
2017-04-01 22:22 ` Samuel Ortiz
2017-04-03 17:27 ` Paul Gortmaker
2017-04-04 1:55 ` Paul Gortmaker
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=20170329065104.GB30988@zurbaran.ger.intel.com \
--to=sameo@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=paul.gortmaker@windriver.com \
--cc=tony.luck@intel.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 NNTP newsgroup(s).