All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: "Alex Deucher" <alexdeucher@gmail.com>,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	"David Airlie" <airlied@linux.ie>,
	LKML <linux-kernel@vger.kernel.org>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	"Linux I2C" <linux-i2c@vger.kernel.org>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 6/6] drm/radeon: convert to use i2c_new_client_device()
Date: Fri, 27 Mar 2020 18:03:42 +0100	[thread overview]
Message-ID: <20200327170342.GA5572@ravnborg.org> (raw)
In-Reply-To: <20200327154509.GB3971@ninjato>

On Fri, Mar 27, 2020 at 04:45:09PM +0100, Wolfram Sang wrote:
> 
> > > > > Move away from the deprecated API.
> > > > >
> > > > > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > > >
> > > > patches 1,6, are:
> > > > Acked-by: Alex Deucher <alexander.deucher@amd.com>
> > > Should we commit all to drm-misc-next?
> > 
> > I'm fine to see it go through whatever tree makes sense.
> 
> I'd suggest drm-misc-next to minimize merge conflicts. But I can take it
> via I2C tree, too, if desired.

If no-one else speaks up until tomorrow I will land them in
drm-misc-next.
Just wanted to make sure it was OK.

	Sam

WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: "David Airlie" <airlied@linux.ie>,
	LKML <linux-kernel@vger.kernel.org>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Linux I2C" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH 6/6] drm/radeon: convert to use i2c_new_client_device()
Date: Fri, 27 Mar 2020 18:03:42 +0100	[thread overview]
Message-ID: <20200327170342.GA5572@ravnborg.org> (raw)
In-Reply-To: <20200327154509.GB3971@ninjato>

On Fri, Mar 27, 2020 at 04:45:09PM +0100, Wolfram Sang wrote:
> 
> > > > > Move away from the deprecated API.
> > > > >
> > > > > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > > >
> > > > patches 1,6, are:
> > > > Acked-by: Alex Deucher <alexander.deucher@amd.com>
> > > Should we commit all to drm-misc-next?
> > 
> > I'm fine to see it go through whatever tree makes sense.
> 
> I'd suggest drm-misc-next to minimize merge conflicts. But I can take it
> via I2C tree, too, if desired.

If no-one else speaks up until tomorrow I will land them in
drm-misc-next.
Just wanted to make sure it was OK.

	Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: "David Airlie" <airlied@linux.ie>,
	LKML <linux-kernel@vger.kernel.org>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	"Alex Deucher" <alexdeucher@gmail.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Linux I2C" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH 6/6] drm/radeon: convert to use i2c_new_client_device()
Date: Fri, 27 Mar 2020 18:03:42 +0100	[thread overview]
Message-ID: <20200327170342.GA5572@ravnborg.org> (raw)
In-Reply-To: <20200327154509.GB3971@ninjato>

On Fri, Mar 27, 2020 at 04:45:09PM +0100, Wolfram Sang wrote:
> 
> > > > > Move away from the deprecated API.
> > > > >
> > > > > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > > >
> > > > patches 1,6, are:
> > > > Acked-by: Alex Deucher <alexander.deucher@amd.com>
> > > Should we commit all to drm-misc-next?
> > 
> > I'm fine to see it go through whatever tree makes sense.
> 
> I'd suggest drm-misc-next to minimize merge conflicts. But I can take it
> via I2C tree, too, if desired.

If no-one else speaks up until tomorrow I will land them in
drm-misc-next.
Just wanted to make sure it was OK.

	Sam
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  reply	other threads:[~2020-03-27 17:03 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 21:09 [PATCH 0/6] gpu: convert to use new I2C API Wolfram Sang
2020-03-26 21:09 ` Wolfram Sang
2020-03-26 21:09 ` Wolfram Sang
2020-03-26 21:09 ` [PATCH 1/6] drm/amdgpu: convert to use i2c_new_client_device() Wolfram Sang
2020-03-26 21:09   ` Wolfram Sang
2020-03-26 21:09   ` Wolfram Sang
2020-03-26 21:10 ` [PATCH 2/6] drm/gma500: " Wolfram Sang
2020-03-26 21:10   ` Wolfram Sang
2020-03-26 21:10 ` [PATCH 3/6] drm/i2c/sil164: " Wolfram Sang
2020-03-26 21:10   ` Wolfram Sang
2020-03-26 21:10 ` [PATCH 4/6] drm/i2c/tda998x: " Wolfram Sang
2020-03-26 21:10   ` Wolfram Sang
2020-03-26 21:10 ` [PATCH 5/6] drm/nouveau/therm: " Wolfram Sang
2020-03-26 21:10   ` Wolfram Sang
2020-03-26 21:10 ` [PATCH 6/6] drm/radeon: " Wolfram Sang
2020-03-26 21:10   ` Wolfram Sang
2020-03-26 21:10   ` Wolfram Sang
2020-03-27 14:25   ` Alex Deucher
2020-03-27 14:25     ` Alex Deucher
2020-03-27 14:25     ` Alex Deucher
2020-03-27 15:25     ` Sam Ravnborg
2020-03-27 15:25       ` Sam Ravnborg
2020-03-27 15:25       ` Sam Ravnborg
2020-03-27 15:27       ` Alex Deucher
2020-03-27 15:27         ` Alex Deucher
2020-03-27 15:27         ` Alex Deucher
2020-03-27 15:45         ` Wolfram Sang
2020-03-27 15:45           ` Wolfram Sang
2020-03-27 15:45           ` Wolfram Sang
2020-03-27 17:03           ` Sam Ravnborg [this message]
2020-03-27 17:03             ` Sam Ravnborg
2020-03-27 17:03             ` Sam Ravnborg
2020-03-28 21:49 ` [PATCH 0/6] gpu: convert to use new I2C API Sam Ravnborg
2020-03-28 21:49   ` Sam Ravnborg
2020-03-28 21:49   ` Sam Ravnborg

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=20200327170342.GA5572@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=wsa@the-dreams.de \
    /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.