Linux Modules
 help / color / mirror / Atom feed
From: Maninder Singh <maninder1.s@samsung.com>
To: "Luis Chamberlain" <mcgrof@kernel.org>,
	"Christophe Leroy" <christophe.leroy@csgroup.eu>,
	"Michal Suchánek" <msuchanek@suse.de>
Cc: "pmladek@suse.com" <pmladek@suse.com>,
	"rostedt@goodmis.org" <rostedt@goodmis.org>,
	"senozhatsky@chromium.org" <senozhatsky@chromium.org>,
	"andriy.shevchenko@linux.intel.com" 
	<andriy.shevchenko@linux.intel.com>,
	"linux@rasmusvillemoes.dk" <linux@rasmusvillemoes.dk>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"wangkefeng.wang@huawei.com" <wangkefeng.wang@huawei.com>,
	Vaneet Narang <v.narang@samsung.com>,
	"swboyd@chromium.org" <swboyd@chromium.org>,
	"ojeda@kernel.org" <ojeda@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>,
	"avimalin@gmail.com" <avimalin@gmail.com>,
	"atomlin@redhat.com" <atomlin@redhat.com>
Subject: RE: [PATCH v3] kallsyms: enhance %pS/s/b printing when KALLSYSMS is disabled
Date: Wed, 16 Mar 2022 14:31:21 +0530	[thread overview]
Message-ID: <385836468.3982590.1647421281746@mail-kr5-2> (raw)
In-Reply-To: <YjGe961XL8GW7Qeh@bombadil.infradead.org>

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

Hi,

> Yes sorry about that, modules-testing is what had Aaron's code. And
> Aaron noted that from his series 13/14 and 14/14 from his series
> had their Message-Id modified accidently via git-send-email. Given
> *current events* and since I use b4 am to verify KSIM signatures
> I asked Aaron to wait and post a v12 to aggregate further reviews
> and acked-by's. The reason being that if his v11 series has issues
> I rather start from a very clean patchset.
>  
> Yes I am paranoid :)
>  
> Anyway so Aaron, let's give it a few more days, and please then post a
> v12 collecing all new tags, then I'll apply your changes and then try to
> apply Christophe's.
>  
> There was some work by Michal Suchánek which would go after, but
> its unclear if that's yet vetted by their other respective maintainers.
> Michal?
>  
> Anyway, your stuff is at the end of the train after Michal's if that
> stuff is really ready. So please don't be surprised if you later have
> to rebase once again, or two or 3 times more. Thanks for your patience.
 
No Worries :)

Let me know when it has to be done.
We will prepare and verify on new rebase.

Thanks,
Maninder Singh

[-- Attachment #2: rcptInfo.txt --]
[-- Type: application/octet-stream, Size: 1746 bytes --]


   =================================================================================================================================
      Subject    : Re: [PATCH v3] kallsyms: enhance %pS/s/b printing when KALLSYSMS is disabled
      From       : null
      Sent Date  : 2022-03-16 13:55  GMT+5:30
   =================================================================================================================================
                  Name                Type          Job Title                       Dept.                               Company                
   =================================================================================================================================
      christophe.leroy@csgroup.eu    TO
      msuchanek@suse.de              TO
      Maninder Singh                 CC         Staff Engineer             System S/W Group /SRI-Delhi               Samsung Electronics 
      pmladek@suse.com               CC
      rostedt@goodmis.org            CC
      senozhatsky@chromium.org       CC
      andriy.shevchenko@linux.i...   CC
      linux@rasmusvillemoes.dk       CC
      akpm@linux-foundation.org      CC
      wangkefeng.wang@huawei.com     CC
      Vaneet Narang                  CC         Associate Architect        System S/W Group /SRI-Delhi               Samsung Electronics
      swboyd@chromium.org            CC
      ojeda@kernel.org               CC
      linux-kernel@vger.kernel.org   CC
      linux-modules@vger.kernel...   CC
      avimalin@gmail.com             CC
      atomlin@redhat.com             CC
   =================================================================================================================================

  parent reply	other threads:[~2022-03-16  9:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220315155109epcas5p249963f50d68ee368edb569b1a9e7d63c@epcas5p2.samsung.com>
2022-03-15 15:51 ` [PATCH v3] kallsyms: enhance %pS/s/b printing when KALLSYSMS is disabled Maninder Singh
2022-03-15 17:52   ` Luis Chamberlain
2022-03-16  4:39     ` Maninder Singh
2022-03-16  6:40     ` Christophe Leroy
2022-03-16  8:25       ` Luis Chamberlain
2022-03-16  8:27         ` Luis Chamberlain
2022-03-16  9:01         ` Maninder Singh [this message]
2022-03-21 13:39         ` Aaron Tomlin
2022-03-21 17:35           ` Luis Chamberlain

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=385836468.3982590.1647421281746@mail-kr5-2 \
    --to=maninder1.s@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=atomlin@redhat.com \
    --cc=avimalin@gmail.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mcgrof@kernel.org \
    --cc=msuchanek@suse.de \
    --cc=ojeda@kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=swboyd@chromium.org \
    --cc=v.narang@samsung.com \
    --cc=wangkefeng.wang@huawei.com \
    /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