mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
	Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the gpio-brgl tree with the gpio-brgl-fixes tree
Date: Tue, 17 Nov 2026 11:10:06 +0000	[thread overview]
Message-ID: <6c6dceb4-1311-44a6-a25a-e85b984ecc19@sirena.org.uk> (raw)
In-Reply-To: <pb6e2wsemefeqkrzcvaqr7nfcsmufttvoooy6y3emypswaqnld@bflexif6xdgg>

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

On Tue, Nov 17, 2026 at 09:16:59AM +0100, Bartosz Golaszewski wrote:
> On Mon, Nov 16, 2026 at 08:09:53PM +0000, Mark Brown wrote:

> > - 				set_bit(GPIOD_FLAG_SHARED_PROXY, &gdev->descs[0].flags);
> >  -				__set_bit(GPIOD_FLAG_SHARED_PROXY,
> >  -					  &gdev->descs[0].flags);
> > ++				__set_bit(GPIOD_FLAG_SHARED_PROXY, &gdev->descs[0].flags);

> This should actually keep the atomic set_bit(). In any case, I will send
> a PR with fixes to Torvalds this week and pull back v7.4-rc4 into
> gpio/for-next once tagged.

Yeah, I didn't look up which one was atomic.

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

  reply	other threads:[~2026-11-17 11:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 20:09 Mark Brown
2026-11-16 21:42 ` [PATCH linux-next] gpio: shared: keep the atomic set_bit() in the gpio-brgl merge Sasha Levin
2026-11-17  8:16 ` linux-next: manual merge of the gpio-brgl tree with the gpio-brgl-fixes tree Bartosz Golaszewski
2026-11-17 11:10   ` Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-30 19:58 Mark Brown
2025-03-14  5:06 Stephen Rothwell
2025-03-14  9:57 ` Bartosz Golaszewski
2025-03-03  5:57 Stephen Rothwell
2025-03-03  8:33 ` Bartosz Golaszewski
2024-05-10  5:32 Stephen Rothwell
2024-05-10  6:33 ` Bartosz Golaszewski
2024-05-10  7:08   ` Stephen Rothwell
2024-05-10  7:10     ` Stephen Rothwell
2024-05-10 15:08       ` Andy Shevchenko
2023-10-19  5:06 Stephen Rothwell
2023-10-19  8:41 ` Bartosz Golaszewski
2021-01-20  2:51 Stephen Rothwell

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=6c6dceb4-1311-44a6-a25a-e85b984ecc19@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=brgl@bgdev.pl \
    --cc=brgl@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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

all inboxes | Powered by JetHome®