From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: 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-wireless@vger.kernel.org
Subject: Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.
Date: Mon, 03 Apr 2017 17:27:00 +0000 [thread overview]
Message-ID: <20170403172659.GN2713@windriver.com> (raw)
In-Reply-To: <20170401222244.GF22034@zurbaran.ger.intel.com>
[Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.] On 02/04/2017 (Sun 00:22) Samuel Ortiz wrote:
> Hi Paul,
>
> On Mon, Jan 09, 2017 at 12:52:22PM -0500, Paul Gortmaker wrote:
> > Currently ia64 fails building allmodconfig with variations of:
> >
[...]
> >
> > drivers/nfc/nfcmrvl/fw_dnld.c | 2 +-
> > drivers/nfc/nxp-nci/firmware.c | 2 +-
> > drivers/nfc/nxp-nci/i2c.c | 2 +-
> > 3 files changed, 3 insertions(+), 3 deletions(-)
> This build issue is now fixed in nfc-next with a couple of different
> patches.
OK, I'll remove it from my local queue and retest and let you know if I
see any issues still.
Thanks,
Paul.
--
>
> Cheers,
> Samuel.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: <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-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.
Date: Mon, 3 Apr 2017 13:27:00 -0400 [thread overview]
Message-ID: <20170403172659.GN2713@windriver.com> (raw)
In-Reply-To: <20170401222244.GF22034@zurbaran.ger.intel.com>
[Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at driver level.] On 02/04/2017 (Sun 00:22) Samuel Ortiz wrote:
> Hi Paul,
>
> On Mon, Jan 09, 2017 at 12:52:22PM -0500, Paul Gortmaker wrote:
> > Currently ia64 fails building allmodconfig with variations of:
> >
[...]
> >
> > drivers/nfc/nfcmrvl/fw_dnld.c | 2 +-
> > drivers/nfc/nxp-nci/firmware.c | 2 +-
> > drivers/nfc/nxp-nci/i2c.c | 2 +-
> > 3 files changed, 3 insertions(+), 3 deletions(-)
> This build issue is now fixed in nfc-next with a couple of different
> patches.
OK, I'll remove it from my local queue and retest and let you know if I
see any issues still.
Thanks,
Paul.
--
>
> Cheers,
> Samuel.
next prev parent reply other threads:[~2017-04-03 17:27 UTC|newest]
Thread overview: 19+ 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:19 ` Paul Gortmaker
2017-01-09 0:47 ` kbuild test robot
2017-01-09 0:47 ` kbuild test robot
2017-01-09 0:56 ` kbuild test robot
2017-01-09 0:56 ` kbuild test robot
2017-01-09 17:52 ` [PATCH v2] " Paul Gortmaker
2017-01-09 17:52 ` Paul Gortmaker
2017-03-28 22:55 ` Paul Gortmaker
2017-03-28 22:55 ` Paul Gortmaker
2017-03-28 22:55 ` Paul Gortmaker
2017-03-29 6:51 ` Samuel Ortiz
2017-03-29 6:51 ` Samuel Ortiz
2017-04-01 22:22 ` Samuel Ortiz
2017-04-01 22:22 ` Samuel Ortiz
2017-04-03 17:27 ` Paul Gortmaker [this message]
2017-04-03 17:27 ` Paul Gortmaker
2017-04-04 1:55 ` 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=20170403172659.GN2713@windriver.com \
--to=paul.gortmaker@windriver.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=sameo@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.