All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: 赵晓 <zhaoxiao@uniontech.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	linux-usb <linux-usb@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb:mux:intel_pmc_mux: Use the helper acpi_dev_get_memory_resources()
Date: Thu, 1 Sep 2022 14:31:51 +0300	[thread overview]
Message-ID: <YxCYJ3ht30SHssbn@kuha.fi.intel.com> (raw)
In-Reply-To: <YxCVOHuaOQGKNf7X@kuha.fi.intel.com>

On Thu, Sep 01, 2022 at 02:19:24PM +0300, Heikki Krogerus wrote:
> On Thu, Sep 01, 2022 at 11:39:17AM +0800, 赵晓 wrote:
> > No generated by yet another bot, The patch refer to the below:&nbsp;
> > https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&amp;id=6505e452371d44be00fe321996f1de248a7606a2
> 
> I don't know what are you trying to point at with that, but I'm
> guessing you are trying to refer to this patch series [1] that Rafael
> indeed picked to his PM tree - mostly. The first patch was taken by
> Greg, though now that I look at his linux-usb tree, it's not there?

No, sorry, the path is there (it was just not in 6.0-rc3 like I
though):
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/commit/?h=usb-linus&id=1b1b672cc1d4fb3065dac79efb8901bd6244ef69

So your patch would have a conflict with that one. This is the proper
solution:
https://lore.kernel.org/linux-usb/20220816101629.69054-7-heikki.krogerus@linux.intel.com/

thanks,

-- 
heikki

      reply	other threads:[~2022-09-01 11:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31  6:11 [PATCH] usb:mux:intel_pmc_mux: Use the helper acpi_dev_get_memory_resources() zhaoxiao
2022-08-31  8:21 ` Heikki Krogerus
2022-08-31  8:33   ` Greg KH
     [not found]     ` <tencent_4E7B2E1523A5D8801223AAB6@qq.com>
2022-09-01 11:19       ` Heikki Krogerus
2022-09-01 11:31         ` Heikki Krogerus [this message]

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=YxCYJ3ht30SHssbn@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=zhaoxiao@uniontech.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.