lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADnq5_NgzZ+1FTzZObivnjJbbuYcafY-fbvgiGA9ryqA9wYedg@mail.gmail.com>
Date:   Thu, 16 Nov 2023 14:17:48 -0500
From:   Alex Deucher <alexdeucher@...il.com>
To:     Wolfram Sang <wsa@...nel.org>,
        Heiner Kallweit <hkallweit1@...il.com>,
        intel-gfx@...ts.freedesktop.org, linux-i2c@...r.kernel.org,
        Jernej Skrabec <jernej.skrabec@...il.com>,
        Jonas Karlman <jonas@...boo.se>,
        Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
        linux-fbdev@...r.kernel.org, amd-gfx@...ts.freedesktop.org,
        linux-rockchip@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org,
        dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
        Thomas Zimmermann <tzimmermann@...e.de>,
        Jocelyn Falempe <jfalempe@...hat.com>,
        linux-sunxi@...ts.linux.dev, linux-mediatek@...ts.infradead.org,
        Sean Paul <sean@...rly.run>,
        Marijn Suijten <marijn.suijten@...ainline.org>,
        linux-arm-msm@...r.kernel.org, freedreno@...ts.freedesktop.org,
        Xinwei Kong <kong.kongxinwei@...ilicon.com>,
        Sumit Semwal <sumit.semwal@...aro.org>,
        Yongqin Liu <yongqin.liu@...aro.org>,
        John Stultz <jstultz@...gle.com>
Subject: Re: [PATCH 00/20] remove I2C_CLASS_DDC support

On Mon, Nov 13, 2023 at 3:55 PM Wolfram Sang <wsa@...nel.org> wrote:
>
>
> > We're not in a hurry. It's just my experience with patch series' affecting
> > multiple subsystems that typically the decision was to apply the full
> > series via one tree. Also to avoid inquires from maintainers like:
> > Shall I take it or are you going to take it?
> > Of course there may be different opinions. Please advise.
>
> Ok, then this turns out to be a negotation thing between the drm/fbdev
> maintainers and me. I *can* take all the patches, of course. But since
> the number of patches touching the non-i2c subsystems is high, I'd like
> to hear their preference, too.
>

I don't have a preference if you would prefer to take these via i2c.

Alex

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ