All of lore.kernel.org
 help / color / mirror / Atom feed
From: SAURAV GIREPUNJE <saurav.girepunje@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: fabioaiuto83@gmail.com, marcocesati@gmail.com,
	ross.schm.dev@gmail.com, insafonov@gmail.com,
	linux-staging@lists.linux.dev, saurav.girepunje@hotmail.com
Subject: Re: Post to linux-staging@lists.linux.dev denied: [PATCH] staging: rtl8723bs: os_dep: remove unused variable
Date: Sat, 7 Aug 2021 09:44:21 +0530	[thread overview]
Message-ID: <YQ4InXVA8FaqdEfo@user> (raw)
In-Reply-To: <YQvFpwNDRSxLxNmp@kroah.com>

On Thu, Aug 05, 2021 at 01:04:07PM +0200, Greg KH wrote:
> On Wed, Aug 04, 2021 at 10:50:36PM +0530, SAURAV GIREPUNJE wrote:
> > On Wed, Aug 04, 2021 at 03:56:00PM +0200, Greg KH wrote:
> > > On Wed, Aug 04, 2021 at 07:15:05PM +0530, SAURAV GIREPUNJE wrote:
> > > > On Wed, Aug 04, 2021 at 12:57:04PM +0000, linux-staging+owner@lists.linux.dev wrote:
> > > > > Greetings!
> > > > >
> > > > > This is the mlmmj program managing the <linux-staging@lists.linux.dev>
> > > > > mailing list.
> > > > >
> > > > > The message from <saurav.girepunje@gmail.com> with subject "[PATCH]
> > > > > staging: rtl8723bs: os_dep: remove unused variable" was unable to be
> > > > > delivered to the list because the list address was not found in either the
> > > > > To: or CC: header.
> > > > >
> > > > > (The denied message is below.)
> > > >
> > > > > Date: Wed, 4 Aug 2021 18:26:57 +0530
> > > > > From: Saurav Girepunje <saurav.girepunje@gmail.com>
> > > > > To: gregkh@linuxfoundation.org;, fabioaiuto83@gmail.com;,
> > > > >  saurav.girepunje@gmail.com;, marcocesati@gmail.com;,
> > > > >  ross.schm.dev@gmail.com;, insafonov@gmail.com;,
> > > > >  linux-staging@lists.linux.dev;, linux-kernel@vger.kernel.org;
> > > > > Cc: saurav.girepunje@hotmail.com
> > >
> > > Why do you have ";" in your email addresses here?
> > >
> > > Try removing them.
> >
> >
> > Thanks Greg, That was the problem.
> >
>
> Can you resend all of your pending patches in the proper way, in a patch
> series, so I know what to apply and in what order they should be applied
> in?  Right now I have a bunch that never made it to a public list, and I
> can not take them, so I will just drop all patches from you that are
> pending in my queue to make it obvious what I need to review.
>
> thanks,
>
> greg k-h


Yes, I will resend all the patch.


      reply	other threads:[~2021-08-07  4:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1628081824-28535-mlmmj-16bf2009@lists.linux.dev>
2021-08-04 13:45 ` Post to linux-staging@lists.linux.dev denied: [PATCH] staging: rtl8723bs: os_dep: remove unused variable SAURAV GIREPUNJE
2021-08-04 13:56   ` Greg KH
2021-08-04 17:20     ` SAURAV GIREPUNJE
2021-08-05 11:04       ` Greg KH
2021-08-07  4:14         ` SAURAV GIREPUNJE [this message]

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=YQ4InXVA8FaqdEfo@user \
    --to=saurav.girepunje@gmail.com \
    --cc=fabioaiuto83@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=insafonov@gmail.com \
    --cc=linux-staging@lists.linux.dev \
    --cc=marcocesati@gmail.com \
    --cc=ross.schm.dev@gmail.com \
    --cc=saurav.girepunje@hotmail.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 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.