public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Dan Williams <dan.j.williams@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: RE: linux-next: duplicate patch in the pm tree
Date: Wed, 7 Jun 2023 14:02:14 -0700	[thread overview]
Message-ID: <6480f056d974_142af8294d9@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20230607144120.01ce4655@canb.auug.org.au>

Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in nvdimm-fixes tree as a different commit
> (but the same patch):
> 
>   8f0e8597a7fa ("ACPI: NFIT: Add declaration in a local header")
> 
> This is commit
> 
>   40d3f4a65a07 ("acpi: nfit: add declaration in a local header")
> 
> in the nvdimm-fixes tree.

I have now dropped this patch from nvdimm-fixes.

  reply	other threads:[~2023-06-07 21:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07  4:41 linux-next: duplicate patch in the pm tree Stephen Rothwell
2023-06-07 21:02 ` Dan Williams [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-18  3:27 Stephen Rothwell
2025-07-18 13:33 ` Jonathan Corbet
2024-08-05  1:58 Stephen Rothwell
2024-08-05  3:13 ` Andrew Morton
2024-04-21 22:15 Stephen Rothwell
2024-04-23 18:30 ` Rafael J. Wysocki
2023-03-26 20:45 Stephen Rothwell
2023-03-27 18:11 ` Wysocki, Rafael J

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=6480f056d974_142af8294d9@dwillia2-xfh.jf.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sfr@canb.auug.org.au \
    /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