LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Simon Sandström" <simon@nikanor.nu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: kpc2000: add missing dependencies for kpc2000
Date: Sat, 25 May 2019 11:24:04 +0200	[thread overview]
Message-ID: <20190525092404.go3qlfknra6g3fot@dev.nikanor.nu> (raw)
In-Reply-To: <20190525083918.dxa5qtomlu5yyqw5@dev.nikanor.nu>

On Sat, May 25, 2019 at 10:39:18AM +0200, Simon Sandström wrote:
> On Sat, May 25, 2019 at 07:00:17AM +0200, Greg KH wrote:
> > 
> > This is already in linux-next (in a different form), are you sure you
> > are working against the latest kernel tree?
> > 
> > thanks,
> > 
> > greg k-h
> 
> It's based on your staging tree. I think that I have to go back and read
> about next trees again, because I thought it took longer time for things
> to get from staging-next to linux-next.
> 
> Anyway, neither the MFD_CORE nor the typo fix is in linux-next so I
> guess that I could just rebase this on linux-next and re-send as v2.
> I'm not sure if MFD_CORE should be "depends on" or "select" though...
> 
> 
> - Simon

Oh, it must be "select MFD_CORE" because there is no prompt for
MFD_CORE? Should I just rebase it on linux-next and re-send as v2 then?


- Simon

  reply	other threads:[~2019-05-25  9:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-24 20:30 [PATCH 0/2] Fixes for staging/kpc2000's Kconfig Simon Sandström
2019-05-24 20:30 ` [PATCH 1/2] staging: kpc2000: fix typo in Kconfig Simon Sandström
2019-05-24 20:30 ` [PATCH 2/2] staging: kpc2000: add missing dependencies for kpc2000 Simon Sandström
2019-05-25  5:00   ` Greg KH
2019-05-25  8:39     ` Simon Sandström
2019-05-25  9:24       ` Simon Sandström [this message]
2019-05-30 21:01         ` Greg KH

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=20190525092404.go3qlfknra6g3fot@dev.nikanor.nu \
    --to=simon@nikanor.nu \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH 2/2] staging: kpc2000: add missing dependencies for kpc2000' \
    /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

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).