All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Yusef Aslam <yuzi54780@outlook.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v3] Staging: rtl8192e: rtllib_rx: fix alignment
Date: Sun, 30 Jun 2024 09:36:22 +0200	[thread overview]
Message-ID: <43cae9ee-e05e-4447-a62d-eac8307e9670@gmail.com> (raw)
In-Reply-To: <ZoCeul3pAjZLOT8E@archie.me>

On 6/30/24 01:54, Bagas Sanjaya wrote:
> On Thu, Jun 27, 2024 at 07:09:50PM +0100, Yusef Aslam wrote:
>> On Thu, 2024-06-27 at 15:43 +0200, Greg KH wrote:
>>> This all should not be in the body of the email, please use a tool
>>> like
>>> 'git send-email' to send patches.
>>
>> Oh k thanks, I was trying to use git send-email but in the end I just
>> copy pasted the email into Evolution as msmtp was not sending emails
>> for some reason.
> 
> Authentication issues?
> 
> Confused...
> 

Hi Yusef,

I use gmail. There I have 2-factor authentication enabled. I am sending 
my patches in via mutt. To be able to use mutt I have to create a 
app-password especially for mutt. I have no clue if you need to do 
something similar for outlook.com. I recommend to use gmail for sending 
in patches.

Feel free to write to me directly for further questions.

Bye Philipp

  reply	other threads:[~2024-06-30  7:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 12:56 [PATCH v3] Staging: rtl8192e: rtllib_rx: fix alignment Yusef Aslam
2024-06-26 17:32 ` Philipp Hortmann
2024-06-27  8:06   ` Yusef Aslam
2024-06-27 13:43 ` Greg KH
2024-06-27 18:09   ` Yusef Aslam
2024-06-29 23:54     ` Bagas Sanjaya
2024-06-30  7:36       ` Philipp Hortmann [this message]
2024-06-30  8:31         ` Yusef Aslam

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=43cae9ee-e05e-4447-a62d-eac8307e9670@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=yuzi54780@outlook.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.