public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Masahisa Kojima <masahisa.kojima@linaro.org>
Subject: linux-next: manual merge of the efi tree with the efi-fixes tree
Date: Tue, 30 May 2023 14:32:17 +1000	[thread overview]
Message-ID: <20230530143217.49ae8cbf@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]

Hi all,

Today's linux-next merge of the efi tree got a conflict in:

  include/linux/efi.h

between commit:

  fd936fd8ac10 ("efi: fix missing prototype warnings")

from the efi-fixes tree and commit:

  5b6e3aa08c62 ("efi: expose efivar generic ops register function")

from the efi tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc include/linux/efi.h
index 571d1a6e1b74,657f7e203374..000000000000
--- a/include/linux/efi.h
+++ b/include/linux/efi.h
@@@ -1338,6 -1350,7 +1350,9 @@@ bool efi_config_table_is_usable(const e
  	return xen_efi_config_table_is_usable(guid, table);
  }
  
 +umode_t efi_attr_is_visible(struct kobject *kobj, struct attribute *attr, int n);
 +
+ void efivars_generic_ops_register(void);
+ void efivars_generic_ops_unregister(void);
+ 
  #endif /* _LINUX_EFI_H */

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-05-30  4:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30  4:32 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-11  4:13 linux-next: manual merge of the efi tree with the efi-fixes tree Stephen Rothwell
2023-12-11  4:39 ` Stephen Rothwell
2023-12-11  9:22   ` Ard Biesheuvel

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=20230530143217.49ae8cbf@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=ilias.apalodimas@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=masahisa.kojima@linaro.org \
    /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