From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0FE87C4332F for ; Thu, 2 Nov 2023 16:47:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229589AbjKBQrQ (ORCPT ); Thu, 2 Nov 2023 12:47:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36938 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229458AbjKBQrP (ORCPT ); Thu, 2 Nov 2023 12:47:15 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B940112F; Thu, 2 Nov 2023 09:47:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1698943629; x=1730479629; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=keUkf/0Fj5YvzCz3WPOw4pxTYOzAGfxcc6hlW6v/KW0=; b=TbQf778mKnGhxEs8kJv2WViWC0z9nxTAuUUqK6IvwNuVnjMfo+zAfAVZ uSYsETvgU8NcxfiWIK18xgolX6ssf+z9Wq9Tu/eHi86HFjcaI6irIretb FEbFZx/x+juAq086C9LBN05TGg7FJQLHmaSo1IAauqIjy8EV92K5MhR80 3/f4FtHK+j+l4lgQy1+L5SD39mWX403bfHKCiaKCttODVw/SjF6xexwW3 xEtEs3iJ4KbhtwYKmgWoBZp8qhAuaTNZrDwaJJdzBlMIBG2JTTlmOMY1P 3cZY7BvFzJY90ZO5tEyBP5E7KYmsjDo68Zs85d71qxk8w3MjCamPc4sSu g==; X-IronPort-AV: E=McAfee;i="6600,9927,10882"; a="387635404" X-IronPort-AV: E=Sophos;i="6.03,272,1694761200"; d="scan'208";a="387635404" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Nov 2023 09:47:09 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10882"; a="831741469" X-IronPort-AV: E=Sophos;i="6.03,272,1694761200"; d="scan'208";a="831741469" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga004.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Nov 2023 09:47:06 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.97-RC3) (envelope-from ) id 1qyaqV-0000000AkFB-1mqR; Thu, 02 Nov 2023 18:47:03 +0200 Date: Thu, 2 Nov 2023 18:47:03 +0200 From: Andy Shevchenko To: Greg Kroah-Hartman Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, Linus Walleij , Bartosz Golaszewski , Daniel Scally , Heikki Krogerus , Sakari Ailus , "Rafael J. Wysocki" , Rob Herring Subject: Re: [PATCH v1 1/3] device property: Implement device_is_big_endian() Message-ID: References: <20231025184259.250588-1-andriy.shevchenko@linux.intel.com> <20231025184259.250588-2-andriy.shevchenko@linux.intel.com> <2023102624-moonshine-duller-3043@gregkh> <2023110235-viewless-postage-9832@gregkh> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2023110235-viewless-postage-9832@gregkh> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Thu, Nov 02, 2023 at 04:58:53PM +0100, Greg Kroah-Hartman wrote: > On Thu, Nov 02, 2023 at 05:33:40PM +0200, Andy Shevchenko wrote: > > On Thu, Oct 26, 2023 at 03:27:30PM +0300, Andy Shevchenko wrote: > > > On Thu, Oct 26, 2023 at 07:25:35AM +0200, Greg Kroah-Hartman wrote: > > > > On Wed, Oct 25, 2023 at 09:42:57PM +0300, Andy Shevchenko wrote: > > > > > Some users want to use the struct device pointer to see if the > > > > > device is big endian in terms of Open Firmware specifications, > > > > > i.e. if it has a "big-endian" property, or if the kernel was > > > > > compiled for BE *and* the device has a "native-endian" property. > > > > > > > > > > Provide inline helper for the users. > > > > > > > > Acked-by: Greg Kroah-Hartman > > > > > > Thank you, Greg. > > > > > > Bart, would it be still possible to take this into next? > > > I would like to have at least this patch applied (with the first user) > > > to allow conversion of others (I have some more users of new API). > > > > Okay, seems we missed v6.7 with this, can you then prepare an immutable > > branch / tag with this, so other maintainers can pull in case it's needed? > > (I have something against tty already and perhaps something else, let's > > see.) > > After -rc1 is out, I'll look into it, can't do anything until then, > sorry... No problem, this is actually a great news! -- With Best Regards, Andy Shevchenko