From: Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: tiny.windzz@gmail.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: Wed, 5 Dec 2018 14:15:41 +0530 [thread overview]
Message-ID: <20181205084540.GA20250@raj-desk2.iind.intel.com> (raw)
In-Reply-To: <CAHp75Vd1Nzd+CDArk+26vwJvq=rULXxOHfq5rQEQjByJtWjH9w@mail.gmail.com>
On Wed, Dec 05, 2018 at 10:42:21AM +0200, Andy Shevchenko wrote:
> On Wed, Dec 5, 2018 at 3:47 AM Frank Lee <tiny.windzz@gmail.com> wrote:
> > On Wed, Dec 5, 2018 at 1:39 AM Andy Shevchenko
> > <andy.shevchenko@gmail.com> wrote:
> > > On Tue, Dec 4, 2018 at 6:58 PM Frank Lee <tiny.windzz@gmail.com> wrote:
>
> > > > $ git remote set-branches --add origin for-next
> > > > $ git br -vv
> > > > * for-next 651022382c7f [origin/for-next] Linux 4.20-rc1
> > >
> > > Here is the problem,
> > >
> > > For a few days at least we have
> > > 4ecd94b8e13b (HEAD -> for-next) platform/x86: dell-laptop: Mark
> > > expected switch fall-throughs
>
> > Where can I find the correct git repository？
>
> I think even old address still exists:
> http://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git
>
> > I haven't found the correct one for a long time,
> > which include the commit(4ecd94b8e13b ) you said.
>
> And newest one is available via
> http://git.infradead.org/linux-platform-drivers-x86.git
>
> http://git.infradead.org/linux-platform-drivers-x86.git/commit/4ecd94b8e13b014a28be48c94f751fb62f7c749e
>
> Though it's already advanced to contain new portion of accepted
> patches (doesn't matter for you, because they don't touch file in
> question).
Hi Andy, i was thinking of having it split into two patches as it touches
two unrelated files. What is your opinion?
Functionality wise, it looks good to me.
>
>
>
> --
> With Best Regards,
> Andy Shevchenko
--
Best Regards,
Rajneesh
next prev parent reply other threads:[~2018-12-05 8:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 15:52 Yangtao Li
2018-12-03 19:09 ` Andy Shevchenko
2018-12-04 3:59 ` Frank Lee
2018-12-04 12:40 ` Andy Shevchenko
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 [this message]
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=20181205084540.GA20250@raj-desk2.iind.intel.com \
--to=rajneesh.bhardwaj@intel.com \
--cc=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=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
all inboxes | Powered by JetHome®