From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: tiny.windzz@gmail.com
Cc: Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>,
Vishwanath Somayaji <vishwanath.somayaji@intel.com>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
David Box <david.e.box@linux.intel.com>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: convert to DEFINE_SHOW_ATTRIBUTE
Date: Tue, 4 Dec 2018 14:40:14 +0200 [thread overview]
Message-ID: <CAHp75VcSVEakAK4MeoG8zA7MaCWNoL2fOr48iFmxTsjbBpa5XA@mail.gmail.com> (raw)
In-Reply-To: <CAEExFWvRFrS-ZTSkrS5Npe7g-rxtxfCfk+AyTz00Lx4oAWhQ_g@mail.gmail.com>
On Tue, Dec 4, 2018 at 5:59 AM Frank Lee <tiny.windzz@gmail.com> wrote:
>
> On Tue, Dec 4, 2018 at 3:09 AM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> >
> > On Sat, Dec 1, 2018 at 5:52 PM Yangtao Li <tiny.windzz@gmail.com> wrote:
> > >
> > > Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
> >
I like your patch, but...
> > By some reason it's not applicable.
> > Please, rebase on top of our for-next branch, thanks!
> For what reason?
...because I can't apply it, it fails with conflicts.
> I thought that for-next branch has not changed much.
That's correct, it's updated only by approved patch series which is
not many _this_ cycle.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2018-12-04 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 15:52 [PATCH] platform/x86: convert to DEFINE_SHOW_ATTRIBUTE Yangtao Li
2018-12-03 19:09 ` Andy Shevchenko
2018-12-04 3:59 ` Frank Lee
2018-12-04 12:40 ` Andy Shevchenko [this message]
2018-12-04 15:30 ` Frank Lee
2018-12-04 16:18 ` Andy Shevchenko
2018-12-04 16:58 ` Frank Lee
2018-12-04 17:39 ` Andy Shevchenko
2018-12-05 1:47 ` Frank Lee
2018-12-05 8:42 ` Andy Shevchenko
2018-12-05 8:45 ` Rajneesh Bhardwaj
2018-12-05 10:04 ` Andy Shevchenko
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=CAHp75VcSVEakAK4MeoG8zA7MaCWNoL2fOr48iFmxTsjbBpa5XA@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=david.e.box@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rajneesh.bhardwaj@intel.com \
--cc=tiny.windzz@gmail.com \
--cc=vishwanath.somayaji@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).